security:oidc
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
security:oidc [2023/11/01 07:13] – removed - external edit (Unknown date) 127.0.0.1 | security:oidc [2023/11/01 07:13] (current) – ↷ Page moved from business_process_management:camunda:security:oidc to security:oidc skipidar | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Open ID Connect - OIDC ===== | ||
+ | Source: https:// | ||
+ | |||
+ | OpenID Connect is based on top of Oauth 2.0. | ||
+ | |||
+ | Gaps in Oauth 2.0 access token. | ||
+ | Still in the access token - some parts are missing. | ||
+ | It just proves, that the Client user was authorized | ||
+ | |||
+ | |||
+ | Oauth 2.0 access token | ||
+ | < | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | **OpenID Connect Extends OAuth 2.0 with new signed id_token** for the Client and UserInfo endpoint to fetch user attributes | ||
+ | |||
+ | Provides a standard set of scopes and claims for identities | ||
+ | * profile | ||
+ | |||
+ | * address | ||
+ | * phone | ||
+ | |||
+ | Built-in registration, | ||
+ | Bring Your Own Identity (BYOI) | ||
+ | |||
+ | Supports high assurance levels and key SAML use cases (enterprise) OAuth 2.0 + Facebook Connect + SAML 2.0 (good parts) | ||
+ | |||
+ | OIDC Access Token. The important parts is: | ||
+ | **" | ||
+ | ** | ||
+ | < | ||
+ | { | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | |||
+ | {{https:// |