The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", Implementing OpenID Authentication 1.1 Compatibilityĭiffie-Hellman Key Exchange Default Value User-centric digital identity in a free and decentralized manner. OpenID Authentication isĭesigned to provide a base service to enable portable, Through additional service types built on top of this Information not covered in this specification, can be addressed The exchange of profile information, or the exchange of other User-Agents can simplify the end user interaction, though are Party or OpenID Provider session management. ![]() ![]() The use of cookies or any other specific mechanism of Relying Responses, so it does not require any special capabilities of OpenID Authentication uses only standard HTTP(S) requests and Identity to a Relying Party without having to leave their While nothing in the protocol requires JavaScript or modernīrowsers, the authentication scheme plays nicely with Preserve their Identifier if they switch OpenID Providers. An end userĬan freely choose which OpenID Provider to use, and can Register Relying Parties or OpenID Providers. To other sensitive information such as an email address. Needing access to end user credentials such as a password or OpenID Authentication provides a way to prove that an end userĬontrols an Identifier. OpenID Authentication 2.0 - Final Abstract Final: OpenID Authentication 2.0 - Final 5, 2007
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |