608260d0f1
As sketched here: https://developer.okta.com/blog/2018/02/27/a-breakdown-of-the-new-saml-authentication-bypass-vulnerability Thought it was interesting to see how our SAML connector behaved. And it seems to be behaving well. :) Signed-off-by: Stephan Renatus <srenatus@chef.io> |
||
|---|---|---|
| .. | ||
| assertion-signed.tmpl | ||
| assertion-signed.xml | ||
| bad-ca.crt | ||
| bad-ca.key | ||
| bad-status.tmpl | ||
| bad-status.xml | ||
| ca.crt | ||
| ca.key | ||
| gen.sh | ||
| good-resp.tmpl | ||
| good-resp.xml | ||
| idp-cert.pem | ||
| idp-resp-signed-assertion0.xml | ||
| idp-resp-signed-assertion.xml | ||
| idp-resp-signed-message-and-assertion.xml | ||
| idp-resp-signed-message.xml | ||
| idp-resp.xml | ||
| oam-ca.pem | ||
| oam-resp.xml | ||
| okta-ca.pem | ||
| okta-resp.xml | ||
| tampered-resp.xml | ||
| two-assertions-first-signed.tmpl | ||
| two-assertions-first-signed.xml | ||