We have run into several issues trying to use Organizations. This is the most recent one. If there was a better way to invite users to Auth0, we definitely wouldn’t use them, but unfortunately using Organizations is the easiest way to invite new users.
Still, it might be worth it at this point to implement our own invite flow because of the continued issues with Organizations.
Some context:
Hello. We have implemented Organizations as described here: Invite-only - Allow signup from invited but no one else
SPAs
require organization to login
display org prompt
No connections enabled on the SPA, only on the org
However, this seems to break SSO. We are using Universal Login and SSO was working before, we could sign into one app and were signed in everywhere else.
This is especially disruptive with the added org prompt. Because of how our apps link to each other, users are having to …
Permission claim in token is empty when logging on to an application as an organization team member.
Unfortunately this ticket has been closed without a real solution/fix to the bug. It’s been 3 months and I’m facing the exact same issue. Would prefer a real fix than this workaround.
Thanks
Hello,
Permission claim in token is empty when logging on to an application as an organization team member.
When accessing the application as an individual, the permission claim is populated.
RBAC is…
Yep that’s what I meant. I know it can look like a workaround but that’s actually the flow we recommend for invites. That’s also what Organisations team suggested here.
2 Likes