-
-
Notifications
You must be signed in to change notification settings - Fork 764
Associate external logins to local login #41
Comments
Yep, this is certainly something you can do, but I don't see IdSvr doing it out of the box, so to speak. Main reason is that there are so many variations on requirements, that we couldn't get it right for everyone's different needs. So, having said that, I think there's enough flexibility in the design to allow your hooks into the workflow for you to achieve what you want to do. I certainly need to do another video showing how you'd achieve this scenario. |
I agree with you statement about not having IdSvr doing it out of the box but being flexible enough to allow me to implement. Thanks for the quick reply! |
Yep, it's certainly on my TODO list. :) |
Brock, I was considering adding a link button in IdMgr that would make it possible to select logins and merge them into one userid. Would this make sense? Of cause it dont solve all of the questions asked in the original post here, but I was thinking it was nice for small projects where there not yet have been implemented user management sites and such, and an administrator could merge users into one user (and also updating the UserLogins table). If it make sense I will try make the extension to IdMgr. |
Yea, I see what you're saying. Certainly something interesting and useful for an admin. |
Brock, would you mind to make some signal when the video Zam6ak asked for few days back, becomes available? I have even more complex scenario in mind but do not want to make more waves until I see what you will explain |
We are in preview 1 right now - the "associate" feature is on the todo list. No ETA yet. |
After watching all the videos listed on the WIki page, I have a question regarding following scenario:
The app requires local login exists so that users can be set up by a vendor and given proper claims. At the same time the would like to offer convenience of adding/relating external logins (Google, Twitter, Facebook) so that user (and the vendor who set up the user) do not have to manage the password. So to recap:
From what I have seen in the integration video, each external login by the same user (in this case Brock) generated a separate local account.
Alternative to this scenario would be giving user ability to register via custom app, which would then add necessary initial claims.
Toughts?
zam
The text was updated successfully, but these errors were encountered: