Closed Sanofi-EL closed 6 months ago
Would like to comment that I was able solve the issue.
And the problem was, that for me personally the Active Directory (AD) Service was rejecting the connection. The message was somewhat cryptic: “unknown process step found:ConvergedConditionalAccess”. Where actually a double MFA validation imposed by my organisation/company was denying completely this second authentication. It was not exactly "unknown". This step was denied completely by AD Server, not that it was “unknown”. It was denying it, because of an internal flag, where I was not allowed to do certain AD operations.
Situation got solved, by removing me from the "black list" and allowing "outside AD Group" authentication, which permitted the second (or MFA) authentication.
There is no bug in the saml2aws tool. Closing the issue.
While trying to use saml2aws in my company I get the following error:
This is the brief error message: "Error authenticating to IdP.: failed get SAMLAssertion"
This is the verbose output:
Here is this step: "unknown process step found:ConvergedConditionalAccess"
I am aware of this issue: #1075 . I am not using Chrome, I do not have it installed at all. The only weirdness that I could have that my company laptop belonged to another person who installed a not US English Windows on it. I switched back to US regional settings...
I have dowloaded that source code and compiled it and is is the same issue. Any tips on how to debug?