Set Authentication
Last updated
Last updated
The Set Authentication Action transitions the user from an Authentication App to a Secure App. In an authentication workflow, a user will log in using an Authentication App (entering their password or logging in through Google or SSO). When the user has logged in successfully, they will be redirected to the Secure App.
All these flows are controlled through the App Authentication settings in the Configuration Builder.
After an authentication Data Flow is run, use a Condition Action to run the Set Authentication Action if authentication was successful, or display an error message if it was not.
When the user authenticates through the Authentication App, they will be redirected to the Secure App.
If the user attempts to visit the Secure App before authenticating, they will be sent to the Authentication App with a Redirect URL. That Redirect URL should point to the Secure App. After authenticating, the user will be redirected to the URL stored in the Redirect URL.
However, if the user goes to the Authentication App first, there will be no Redirect URL set. In this case, or if the Secure App doesn't specify a Redirect URL, this Backup Redirect URL is used instead.
The Backup Redirect URL should point to the Secure App.
When the Authentication App successfully redirects to the Secure App, the value specified in Payload will be sent to the Secure App via its session.start.
After the user successfully authenticates through the Authentication App, a cookie will be set on their device that will keep them logged in. This value determines how long that cookie will last before expiring.
After the cookie expires, the user will need to authenticate through the Authentication app again in order to receive a new cookie.
