Tools, FAQ, Tutorials:
Components Involved in OpenID Connect Authentication
What are components involved in OpenID Connect authentication flows?
✍: FYIcenter.com
There are 4 components involved in a typical OpenID Connect authentication flow:
1. OpenID Provider (OP) - The OpenID Connect authentication service provider, who provides services to authenticate the end user. For example, Microsoft Azure Active Directory.
2. Relying Party (RP) - Your application server, who relies the OP to let the end user to access your application.
3. User Agent (UA) - The Web browser or your client program running on the end user device. User Agent is used by the end user to access your application and interact with the OpenID Provider.
4. End User (EU) - The end user who wants to access your application using his/her identity managed by the OpenID Provider.
Below is a diagram that shows you how these 4 components are related to each other:
+--------+ +----------+ | | | | | | --> | Rely | | | <-- | Party | +--------+ | | | | | | | | +----------+ | End | --> | User | ^ | | User | <-- | Agent | | v | | | | +----------+ +--------+ | | | | | | --> | OpenID | | | <-- | Provider | | | | | +--------+ +----------+
⇒ What Are Authentication Flows
⇐ OpenID Connect Authentication Flows
2021-08-11, 1343🔥, 0💬
Popular Posts:
What is Azure API Management Developer Portal Admin? The Developer Portal Admin is an Azure Web port...
How to use "{{...}}" Liquid Codes in "set-body" Policy Statement? The "{{...}}" Liquid Codes in "set...
How to search for the first match of a regular expression using re.search()? The re.search() functio...
How to use the "set-body" Policy Statement for an Azure API service operation? The "set-body" Policy...
What is EPUB 2.0 Metadata "dc:publisher" and "dc:rights" elements? EPUB 2.0 Metadata "dc:publisher" ...