Hi @alan.hay
Thanks for you patience while I was researching the issue that you are experiencing.
The main causes for the issue that you are having are:
- You are using username as an identifier for multiple connection
- You are using an user created within the Dashboard
- Your tenant has a default directory configured
Basically, if an user created within the dashboard tried to authenticate for the first time, the connection used for that user will be the default one set on your tenant. From what I have tested, it appears that the user’s connection and organization are not identified while logging in if they were created within the Dashboard.
If you would have been using email as an identifier instead of usernames, this would have been avoided.
In conclusion, to resolve the issue either the flow that you are looking to implement needs to allow an user to sign up within an organization and connection or just simply remove the default directory set from Dashboard-> Settings → General → API Authorization Settings → Default Directory.
Once you have removed it, the users should be able to authenticate normally even if they were created within the Dashboard/Management API without having to specify the connection or organization.
If you have any other questions, let me know!
Kind Regards,
Nik