When I call /authorize?screen_hint=signup&prompt=login&organization=some_org with existing Auth0 session I expect to see sign up form for this organization - as it is described in Universal Login Experience doc. (If Auth0 session doesn’t exist - all is as expected - it renders signup screen for organization)
But what I get - “invalid request. signup is disabled“ - it is true for tenant-wide signup. It means that prompt param doesn’t have effect, since it is auto-redirected, and organization param also doesn’t have effect, since it tries to go to tenant-wide signup.
I believe it is a bug, but if it is expected behaviour, please also say)
Thanks!
As far as I have tested on my own tenant, as long as the organizations have signup enabled, even an already authenticated user should be redirected to the new organization’s signup/login page. However, if the user is already signed up to your application, there is no need to redirect them to the signup page of the organization (unless they will need to create a new account with a different email), you can just redirect them to the login login prompt.
Basically, via Auth0, users can either signup through your application and be assigned an organization or they can signup through an organization to access the application. Users cannot be organization specific, only connection specific.
Since organizations depend on specific connections to be used, if signups are disabled, it would be expected behaviour for you to receive that error.