@clovis1 what does your setup look like? You could have Single Sign On across separate domains and/or Auth0 clients. From your questions I’m not sure if this is what you are looking to achieve specifically. For example, if you’re using something like Lock, and you have two applications. Your flow could look like this:
- User navigates to
- Code executes and is unsuccessful because an SSO cookie doesn’t exist
- Detect the failure and show the Lock widget.
- User logs in with correct credentials, they’re redirected into the app, and you store the token
- User navigates to a different application of yours,
- Code on the page executes and is successful because a valid cookie existed for your tenant
- The result of gives you a new token to store and use
Depending on your use case, the Authorization Extension can help to manage permissions and roles for those applications.
Can you tell me a bit more about your particular use case?