[seam-issues] [JBoss JIRA] Commented: (SEAMSOCIAL-11) Identity on UserProfile
[
https://issues.jboss.org/browse/SEAMSOCIAL-11?page=com.atlassian.jira.plu...
]
Todd Morrison commented on SEAMSOCIAL-11:
-----------------------------------------
Additionally, this module fails to detect trusted sessions that are not managed by the web
app.
To do this in Seam 2, I had to use the client API to set an <s:token..> tag on
login.
This way, if the user submits login and they are already sitting on a valid facebook token
from another tab there is no URL round-trip to verify. The client Facebook api would give
me a valid token and I could login without any additional steps.
I believe in this module the user would have to click a button to auth even if they are
already logged-in to the provider in another tab, which is confusing.
Identity on UserProfile
-----------------------
Key: SEAMSOCIAL-11
URL: https://issues.jboss.org/browse/SEAMSOCIAL-11
Project: Seam Social
Issue Type: Enhancement
Components: OAuth Core
Affects Versions: 3.0.0.Alpha1
Reporter: Todd Morrison
Assignee: Antoine Sabot-Durand
Labels: Identitier, UserProfile
Having a permanent identifier on the UserProfile against major social network
implementations is vital for qualification against a proprietary membership model.
Could you add an String Id field on the UserProfile interface?
This would allow consumers to decorate their User Entity with something like
'facebookId', 'twitterId' and 'linkedInId'. Upon auth, they can do
a look-up on their own User entity and decide if the user can authenticate based on the
token.
This will also allow users to change ScreenName, Email, etc. in the social network
without damaging the authentication bridge upon revisit.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira