As described. Have had this issue 2 times today alone and had never seen before. Was there an update to SAML causing this? From client:
It looks like NAM is throwing an "Invalid NameID policy" error in my trace. The metadata provided indicated that both 'persistent' and 'Email' NameId formats were acceptable.
It looks like NAM is throwing an "Invalid NameID policy" error in my trace. The metadata provided indicated that both 'persistent' and 'Email' NameId formats were acceptable.
I haven't changed anything on supabase side since this was working
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.