Confirmed users
1,209
edits
Single Sign On: Difference between revisions
Jump to navigation
Jump to search
→FAQ
mNo edit summary |
(→FAQ) |
||
| Line 17: | Line 17: | ||
Reasoning: The SSO webapp will have a user page where you can see what apps you've integrated sign-on for. Client webapps still need to define and build out their profile pages. Some user metadata can be gleaned from the SSO server, but updating, storing extra metadata, etc is TBD and probably belongs in a different web service. | Reasoning: The SSO webapp will have a user page where you can see what apps you've integrated sign-on for. Client webapps still need to define and build out their profile pages. Some user metadata can be gleaned from the SSO server, but updating, storing extra metadata, etc is TBD and probably belongs in a different web service. | ||
* '''Q: Will SSO handle authorization''' | * '''Q: Will SSO handle authorization?''' | ||
* A: No, SSO is for authentication, each client application will implement Authorization | * A: No, SSO is for authentication, each client application will implement Authorization | ||
* '''Q: Why not just use OpenID?''' | |||
* A: OpenID alone prevents us from implementing such features as global logout and other future features that require a central authentication entity. However, we might at some point allow you to log into *SSO* using your OpenID. | |||
== Related == | == Related == | ||
* [[MozillaID]] | * [[MozillaID]] | ||