Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -987,9 +987,9 @@ To confirm that the authorization is working, get an access token from your Entr
From version 4.3.0 of the OIDC SSO module, optionally, you can select `ID-TOKEN` as a **Custom ATP Token Type** for all custom access token parsing. Default is `ACCESS-TOKEN`.
{{% /alert %}}

#### Parsing OIDC Provider Access Tokens
#### Parsing Access Tokens From Mendix OIDC Provider

The OIDC SSO module version 2.3.0 and above provides a default access token parsing microflow to use when you are authenticating using the OIDC Provider module as your IdP.
The OIDC SSO module version 2.3.0 and above provides a default access token parsing microflow to use when you are authenticating using the [OIDC Provider](/appstore/services/oidc-provider/) module as your IdP.

To parse the OIDC Provider access tokens you need to do the following when performing OIDC Client Configuration:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -358,7 +358,7 @@ The scopes you configure are not added automatically to the "scopes_supported" a

This is available in version 2.3.0 and above of the OIDC SSO module. For versions below this, you will need to write a custom user provisioning microflow.

* `OIDC.Default_OIDCProvider_TokenProcessing_CustomATP` as the **custom AccessToken processing microflow** for access token parsing
* `OIDC.Default_MendixOIDCProvider_TokenProcessing_CustomATP` as the **custom AccessToken processing microflow** for access token parsing

##### Configuration of the OIDC Provider to Propagate the End-User’s Identity with Custom Claims{#propagate-custom-claims}

Expand Down
Loading