You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thanks for putting this code together - its been great to build off of. I've run into an issue that likely needs to be solved outside of this code, but given that it replicates at https://saastart.app/ I figured I would start here.
The dashboard client requires an organization. The management/onboarding client does not. When going through the signup flow from the portal itself, the management/onboarding client is used and the signup process works fine as the user does not have (or need) an organization. This all works fine.
However, when an unregistered user clicks "Log in" and then from the log in page clicks "Sign up" - they are sent to a sign up flow with the dashboard client ID since that is the client they began the login flow as. This results in an Unauthorized error of "invalid_request (client requires organization membership, but user does not belong to any organization)"
First, thanks for putting this code together - its been great to build off of. I've run into an issue that likely needs to be solved outside of this code, but given that it replicates at https://saastart.app/ I figured I would start here.
The dashboard client requires an organization. The management/onboarding client does not. When going through the signup flow from the portal itself, the management/onboarding client is used and the signup process works fine as the user does not have (or need) an organization. This all works fine.
However, when an unregistered user clicks "Log in" and then from the log in page clicks "Sign up" - they are sent to a sign up flow with the dashboard client ID since that is the client they began the login flow as. This results in an Unauthorized error of "invalid_request (client requires organization membership, but user does not belong to any organization)"
STR:
The text was updated successfully, but these errors were encountered: