End Success node

The End Success node is used to close the flow with a positive result. Once executed, the flow ends and the authentication/operation is marked as successfully completed.

This node is available in: Authentication, Admin, Self Service, API, Library, Consent, Custom, User Defined

The set of available options may depend on the flow category or type in which the node is used.

Authentication — Login flows

Flow - End Success Login node

User binding configurations

• User profile not mandatory: Determines whether a user profile must be resolved before issuing the authentication token. If enabled, the system issues a session token without creating or linking a user account. If disabled, IO attempts to identify an existing user and associate the session with a user profile.

• Choose how to search for the user: If the previous option is disabled, define how IO matches the user during the lookup phase. You can search by username or by a specific user attribute. An Ignore Case option is also available for case-insensitive matching.

Node configurations

• Redirect URL: Define the destination URL to which the user is redirected once the node ends.

• TTL of the authentication Session: Define the total lifetime of the authentication session in minutes. After this time expires, the session becomes invalid. Default: 480

• Idle time of the authentication Session: Define the maximum period of inactivity allowed for the session in minutes. Default: 240

• Where do you want to save the token?: Determines where the authentication token will be stored on the client side: Local Storage or Cookie. If Cookie is selected, you can configure the cookie domain and related settings.

Authentication — Logout flows

Flow - End Success Logout node

Node configurations

• Redirect URL: Define the destination URL to which the user is redirected once the node ends.

• Delete user Session: If enabled, the active user session is invalidated and deleted at the end of the flow execution.

• Where do you want to delete the token from?: Determines where the authentication token will be deleted from: local storage or a cookie. If Cookie is selected, you can define which cookies will be removed.

Self-service flows

• Flow - End Success Registration node

• Flow - End Success Reset Password node

• Flow - End Success Update Password node

Node configurations

• Redirect URL: Define the destination URL to which the user is redirected once the node ends.

Admin flow

• Flow - End Success Admin node

Node configurations

• Redirect URL (see above)

API flows

Flow - End Success Backend node

Node configurations

• Body: Define the HTTP response body returned by the node or the flow. The value you configure (JSON or plain text) is returned to the client as the response body.

• Status: Define the HTTP status code returned in the response.

• API Headers: Allows you to define custom HTTP headers to include in the response. These headers are returned together with the response body and status code.

• Cookie Configurations: Allows you to include Set-Cookie headers in the response. You can create, modify, or expire cookies that will be sent to the client together with the response.

Consent flows

Flow - End Success node

Node configurations

• Redirect URL: Define the destination URL to which the user is redirected once the node ends.

Library flows

Flow - Nested Success node

Node configurations

No node configurations required.

This node terminates the nested flow with a failure outcome and returns control to the parent flow.

Custom/user defined flows

Flow - End Success Frontend node

Node configurations

• Redirect URL: Define the destination URL to which the user is redirected once the node ends.

Flow - End Success Backend node

Node configurations

• Body
• Status
• API Headers
• Cookie Configurations