Matthew Lewis

I added some debug logging to a local build and got the following output: ``` POST /api/v1/authn HTTP/1.1 Host: sso.myorg.com User-Agent: saml2aws/1.0 (darwin arm64) Versent Content-Length: 92 Accept: application/json Content-Type:...

So I had a chat with Okta about this, and we were scheduling a time to investigate this, and then the next time I tested the process worked for me...

We had this issue start to happen again. I engaged Okta support and ran through some testing with them, and determined that there is a scenario where saml2aws does the...

As an aside I've also requested that Okta consider an API to get the SAMLResponse instead of this Rube Goldberg machine of authenticating the user via API and then pretending...

Unfortunately Okta FastPass is not something which can be invoked programmatically (at this point). Its entirely dependent on the Okta Login Widget and there is no API to generate the...

@wolfeidau could we please have this (or one of the others) merged in and released? I'd really like to be able to enforce the number challenge for risk based session...

This has already been built by a few people - a recent one is here: https://github.com/Versent/saml2aws/pull/877 But unfortunately at the moment there's been little response on requests to merge etc......

@silver886 I had a quick look and the JSON content looks correct. For reference I've captured the full payload and redacted sensitive data, and attached it - here the correctAnswer...

@mapkon #1115 seems to be for Ping Identity, I don't see anything in that PR to reference Okta

Thanks! Do you know if the existing setup (using the hooks plugin) still works with updated versions of Bitbucket? Or does upgrading completely bork this?