-
Notifications
You must be signed in to change notification settings - Fork 403
Fix: Add crucial requirement for custom attributes in OIDC scope for access token inclusion (Product IS issue #27542) #6058
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -55,13 +55,20 @@ | |
| {% endif %} | ||
|
|
||
| {% if product_name == "Asgardeo" or (product_name == "WSO2 Identity Server" and is_version != "7.0.0") %} | ||
| #### Access Token Attributes | ||
|
Check failure on line 58 in en/includes/guides/fragments/manage-app/oidc-settings/access-token.md
|
||
|
|
||
| For **JWT** access tokens, this feature enables you to specify which user attributes are included in the access token. As a result, when a user logs in to an application, only the chosen attributes are shared, providing enhanced security and flexibility. | ||
|
|
||
| !!! note | ||
|
Check failure on line 62 in en/includes/guides/fragments/manage-app/oidc-settings/access-token.md
|
||
| All configured user attributes are included in the access token, regardless of the requested scopes. | ||
|
|
||
| !!! warning | ||
| For custom attributes to appear in the access token, you must explicitly add them to an OIDC scope. Without this mapping, custom attributes will not be included in the access token, even if they are configured under **Access Token Attributes**. | ||
| For custom attributes to appear in the access token, you must explicitly add them to an OIDC scope. Without this mapping, custom attributes will not be included in the access token, even if they are configured under **Access Token Attributes**. | ||
|
|
||
| To map custom attributes to an OIDC scope, configure the scope settings in your application's OIDC configuration and ensure the custom attributes are associated with the appropriate scope. | ||
| To map custom attributes to an OIDC scope, [configure the custom attributes for the appropriate scopes]({{base_path}}/guides/users/attributes/manage-scopes/#edit-scopes) and ensure that your application's OIDC configuration is updated to request those scopes. | ||
|
|
||
| {: width="600" style="display: block; margin: 0; border: 0.3px solid lightgrey;"} | ||
|
|
||
| {% endif %} | ||
|
|
@@ -130,8 +137,8 @@ | |
|
|
||
| - **Revoke token upon user logout** - When enabled, a user logout from a session causes access tokens to be revoked provided the logout request contains either `client_id` or `id_token_hint`. Learn more about [logout requests]({{base_path}}/guides/authentication/oidc/add-logout/). | ||
|
|
||
| #### User access token expiry time | ||
|
Check failure on line 140 in en/includes/guides/fragments/manage-app/oidc-settings/access-token.md
|
||
| This option specifies the validity period of an access token issued to a user in seconds. The default expiry time is 3600 seconds. | ||
|
|
||
| #### Application access token expiry time | ||
|
Check failure on line 143 in en/includes/guides/fragments/manage-app/oidc-settings/access-token.md
|
||
| This option specifies the validity period of an access token issued to an application when using the `Client Credentials` grant type in seconds. | ||
Uh oh!
There was an error while loading. Please reload this page.