Using Auth0 to authenticate your users? Build even more use cases with this service and improve both design and UX of forms built on top of this authentication provider.
Arengu complements Auth0 actions allowing developers to build custom experiences for the end user with forms, flows and hosted pages, to collect new users’ information when they authenticate through Auth0.
What are Auth0 actions?
Auth0 actions are JavaScript functions that execute when a user authenticates to your application.
They run once the authentication process is complete, and you can use them to customize and extend Auth0's capabilities. For example, to build adaptive forms, progressive profiling use cases, etc. with Arengu.
How to use Auth0 actions with Arengu
Passing information between Arengu and Auth0 requires a secure way to ensure that the information has not been tampered with and the operation has been completed by the current user.
To achieve this, there is available in Auth0 Marketplace a predefined set of actions to redirect users to Arengu in a secure way and then resume the authentication flow in Auth0 once the operation is completed.
Arengu's Auth0 actions can be used to build use cases like:
- Progressive profiling: to reduce signup friction when asking users for new information the Xth time they log in to your platform. Check this action in Auth0.
- Policies acceptance: to require your users to accept new terms or privacy policies the next time they log in. Check this action in Auth0.
- Payments or subscriptions: to require payment details with Stripe if the trial is over and enroll your users into paid subscriptions if they are in free plans.
- Custom MFA: to ask for additional verifications if the user logs in from unknown devices, if they have a risky IP, etc.
- Custom signups: to adapt your signup flows to your business needs asking for new information, verifying users’ identity, enriching information, etc.
Install Arengu’s integrations in your dashboard
To start using Arengu’s integrations with Auth0 actions, simply add them to your Auth0 dashboard:
- Go to your Auth0 Dashboard > Marketplace.
- Search for ‘Arengu’.
- Click on the action and then on the ‘Add integration’ button.
You will be automatically redirected to the Actions Library screen, which will be different depending on the use case you want to build. Check below how to configure each one.
Progressive profiling with Auth0 actions
Require your users to complete their profile the second time they log in. This use case consists of a custom form to request specific data from your users which will be displayed, after logging in, only to the users in whose profile this data is not stored.
For example, we can build a form to ask for the company and job title to the users for whom we do not have this data, using custom Auth0 actions. The form will be linked to a flow that will check the user's session token and update the user's metadata in Auth0.
Learn here how to build this use case, how to configure the Auth0 actions, and how to create and connect the form and flows in Arengu.
Custom policies acceptance with Auth0 actions
Require custom privacy policies from your users before allowing them access to your application. This use case consists of a custom form to request acceptance of the new conditions which will be displayed, after logging in, to the users who have not yet accepted it.
In this case, we need to build a form to display the new terms and conditions, and a legal field to accept them. This form will be linked to a flow that will check the session token and update the app metadata in Auth0.
Learn here how to build this use case, how to configure the Auth0 actions, and how to create and connect the form and flows in Arengu.
SaaS paywall integration with Auth0 & Stripe
Add a paywall to dynamically prompt the users for credit card details based on their Auth0 meta information. This use case consists of a payment form that performs custom logic and validations with Stripe, before redirecting the user back to Auth0.
In this case, the user will log in with Auth0, which will process the actions and redirect the user to a custom screen (the paywall) with a signed JWT if the user has not made the payment yet.
Then, the user will provide the payment details in Arengu, which will perform custom logic with Stripe, and redirect the user back to Auth0 passing a signed JWT with the user's data. Auth0 will verify the signed JWT, update the metadata and resume the authentication flow.
Learn here how to build this use case, how to configure the Auth0 actions, and how to create and connect the form and flows in Arengu.
Missing any more use cases?
If you are missing any more tutorials, do not hesitate to send us your feedback using the form that you will find below. Hope to hear from you!
