From 1c3c9a763f94b2e0ac9aa15b457ed4ec64085323 Mon Sep 17 00:00:00 2001 From: malithie Date: Wed, 2 Oct 2024 17:03:26 +0530 Subject: [PATCH] Update timelines. --- .../customize/actions/pre-issue-access-token-action | 6 +++--- .../customize/actions/understanding-actions.md | 12 ++++++------ 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/en/includes/guides/customize/actions/pre-issue-access-token-action b/en/includes/guides/customize/actions/pre-issue-access-token-action index ee1184fa8f..d2b9f721d3 100644 --- a/en/includes/guides/customize/actions/pre-issue-access-token-action +++ b/en/includes/guides/customize/actions/pre-issue-access-token-action @@ -6,7 +6,7 @@ You can use this functionality to: - Add, modify, or remove scopes. - Add, modify, or remove audience values. -- Modify or remove [OIDC scopes]({{base_path}}/guides/users/attributes/manage-scopes/) incorporated into the access token. +- Modify or remove user attributes incorporated into the access token. - Add custom claims (only string, number, boolean, and string type arrays are allowed). - Update the validity period of the access token. @@ -345,7 +345,7 @@ The response can have two possible states: SUCCESS and ERROR< ERROR: Indicates a failure in processing, accompanied by an error message that should be communicated to the application. This error message should adhere to OAuth 2.0 error response definitions to ensure compliance. However, it is your responsibility to ensure this compliance when extending the flow. !!! note - Currently, ERROR responses are not communicated back to the client, but this functionality is planned for inclusion by September 2024. + Currently, ERROR responses are not communicated back to the client, but this functionality is planned for inclusion by end October 2024. #### Response for SUCCESS state: @@ -407,6 +407,6 @@ Http Status Code: 400, 401 or 500 !!! note - Currently, ERROR responses are not communicated back to the client, but this functionality is planned for inclusion by September 2024. + Currently, ERROR responses are not communicated back to the client, but this functionality is planned for inclusion by end October 2024. If the defined error response is not received, or if the external service fails to respond, this is identified as an error in executing the action. In such cases, the flow will proceed as if the action was not applied, ensuring that the process continues without disruption. diff --git a/en/includes/guides/customize/actions/understanding-actions.md b/en/includes/guides/customize/actions/understanding-actions.md index 10138b9c5a..f8ce19751a 100644 --- a/en/includes/guides/customize/actions/understanding-actions.md +++ b/en/includes/guides/customize/actions/understanding-actions.md @@ -9,7 +9,7 @@ The capabilities of an action are determined by its execution point within the { {{product_name}} defines several types of actions, each tailored to customize a specific flow within the product. While all action types use the same general syntax for requests and responses exchanged between {{product_name}} and the external web service, they differ in the specifics of the JSON objects involved. When implementing your external service, you must develop your code according to the REST API contract associated with the type of action you are using. The following flows support customization with custom code. !!! note - Currently, the product supports only the pre issue access token trigger. The other action types listed below are planned for inclusion by September 2024. + Currently, the product supports only the pre issue access token trigger. The other action types listed below are planned for inclusion by early December 2024. @@ -24,7 +24,7 @@ The capabilities of an action are determined by its execution point within the { - + - + - + - +
Login AuthenticateOctober 2024Early November 2024

  • Call an external service to authenticate the user.

    • @@ -48,7 +48,7 @@ The capabilities of an action are determined by its execution point within the {
Registration Pre registrationNovember 2024Early December 2024

  • Deny registration by location.

    • @@ -61,7 +61,7 @@ The capabilities of an action are determined by its execution point within the {
Password update Pre password updateOctober 2024Early November 2024

  • Challenge with an additional verification factor before allowing to update password.

    • @@ -72,7 +72,7 @@ The capabilities of an action are determined by its execution point within the {
Profile update Pre profile updateNovember 2024Early December 2024

  • Challenge with an additional verification factor before allowing to update sensitive attributes.

    • @@ -183,6 +183,6 @@ Requests will not be retried if the external service responds with HTTP status c ### Troubleshooting !!! note - Troubleshooting logs are not yet incorporated but are planned for inclusion by end August 2024. + Troubleshooting logs are not yet incorporated but are planned for inclusion by end October 2024.