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
I am using a WS-Federation identity provider connected to Azure AD. This is just a development setup so I can run my own AD. Oddly, I have a live setup (not managed by me) that sends almost the exact same response but without the wsa namespace on that one section of XML. I've verified that they're both using SAML 2.0 tokens, and in fact everything else about the response structure is exactly the same.
So I'm curious if it's possible that something about my configuration is causing the wsa namespace to be applied, or perhaps different setups cause slightly different responses (in which case I assume a patch to support either with-or-without the namespace would be appropriate?).
I am using version 0.2.3 of the gem but I did check the development and beta branches to see if this had already been addressed. Adding the wsa namespace fixes the issue for my development AD and the request completes.
I also noticed that the SAML 1.0 token handler explicitly does use the wsa namespace when finding the audience.
I'm new to Azure/WSFed so if there is any other information I can provide please let me know.
The text was updated successfully, but these errors were encountered:
I get this error when I get the response back from the ACS:
The parsing fails because in the response I am getting there is a
wsa
namespace applied to theEndpointReference
andAddress
nodes:I am using a WS-Federation identity provider connected to Azure AD. This is just a development setup so I can run my own AD. Oddly, I have a live setup (not managed by me) that sends almost the exact same response but without the
wsa
namespace on that one section of XML. I've verified that they're both using SAML 2.0 tokens, and in fact everything else about the response structure is exactly the same.So I'm curious if it's possible that something about my configuration is causing the
wsa
namespace to be applied, or perhaps different setups cause slightly different responses (in which case I assume a patch to support either with-or-without the namespace would be appropriate?).I am using version 0.2.3 of the gem but I did check the development and beta branches to see if this had already been addressed. Adding the
wsa
namespace fixes the issue for my development AD and the request completes.I also noticed that the SAML 1.0 token handler explicitly does use the
wsa
namespace when finding the audience.I'm new to Azure/WSFed so if there is any other information I can provide please let me know.
The text was updated successfully, but these errors were encountered: