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
the Azure IdP rejects Authn Requests that include a Subject (although the docs claim that it'd be ignored)
by default, Azure's AD doesn't respond with NameId of format urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
There's a combined commit for 2. and 3. here, but this solution might not be the only possible one. What do you think is the best way for azure compatibility? Just remove the Subject (2.) and let the user cope with that NameID comes in the response, or expose the NameIdPolicy to make it configurable (in esaml_sp)?
Hi there.
Trying to get esaml (branch develop) to work with Azure, the following things came up:
Subject(although the docs claim that it'd be ignored)urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddressThere's a combined commit for 2. and 3. here, but this solution might not be the only possible one. What do you think is the best way for azure compatibility? Just remove the Subject (2.) and let the user cope with that NameID comes in the response, or expose the NameIdPolicy to make it configurable (in esaml_sp)?
Thanks