Thank you for the reply.
If not done so through an auth0 action how would I achieve this outside within my codebase? Is changing the SPA client ID a valid design pattern?
In this scenario SPA 1 would have to be a default for all users. Depending on what organization the user tries to authenticate with, could I preserve logged in status while dynamically switching the client ID to SPA 2’s?
To give more context, we need two versions of our SPA. That utilize different 3rd party cloud services. Some b2b customers have a restriction against using certain cloud services so we were thinking of verifying this by org name, and either keep them in SPA 1 after authenticating, or redirect them to SPA 2 without making them authenticate a second time.