Community
Participate
Working Groups
Right now, if a user wants to authenticate using form and some OpenID and be mapped to the same profile, he can't do it.
My proposal for the first step: When user logs in with OpenId we generate an Orion account without a password. This OpenId account is mapped to the user profile. Next time user logs in with this OpenId we'll find this Orion account by mapped OpenId. User may set password for the account and change login and then use regular form authentication. Next step will be adding and removing OpenId accounts to the existing user profile.
Maybe it was not recorded yet in Bugzilla, but yes, this is what we need. Important thing is to not add any OpenId specific API to our IOrionCredentialService. I imagine that the authentication mechanism (like OpenId, LDAP or something else) just sets some extra properties on the user account that are later used to map OpenID or LDAP id to the internal Orion account.
First step made. Now when user loggs in via OpenId we create a profile for him. He me set a password and change login. Next time he loggs in with the same OpenId his profile is found.
Second step made. I created an iframe plugin that adds a list of connected OpenId identifiers and allows to add and remove them. The only problem is that the plugin needs to be provided by the server because server only knows anything about openid providers and authentication in general. The problem is that the iframe provides UI that is (just like the login dialog) independent from the client.
the feature is done
I couldn't find this feature anywhere. Is it on the profile page? I'm looking for the place where I can add/remove OpenIDs on my Orion account. I wanted a screen shot for New & Noteworthy.
(In reply to comment #6) > I couldn't find this feature anywhere. Is it on the profile page? I'm looking > for the place where I can add/remove OpenIDs on my Orion account. I wanted a > screen shot for New & Noteworthy. Never mind, I had to restart my server to see this change. Ignore me.