The status code of the Response was not Success, was Responder -> Error occurred

[Jason Kaye]

Thanks for the help. I took "Incoming RequestedAuthnContext disallowed by profile configuration" to mean something in the IdP's profile was keeping it from accessing the RequestedAuthnContext. We deal with multiple IdPs and this is in no way different from our implementations with them, so I am not sure why this is coming up here. I'm not sure what configuration setting would even set that.
________________________________
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Wednesday, March 27, 2019 12:30 PM
To: Shib Users
Subject: Re: The status code of the Response was not Success, was Responder -> Error occurred

On 3/27/19, 12:21 PM, "users on behalf of Jason Kaye" <users-bounces at shibboleth.net on behalf of jakaye at syr.edu> wrote:

> -Profile Action ProcessRequestedAuthnContext: Incoming RequestedAuthnContext disallowed by profile configuration

You did that. It's telling you what you did.

> We're using the Onelogin Python SAML Library (), and our AuthnContext looks like this

And you told the IdP to disallow anything in that element being sent.

-- Scott



--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20190327/7ca6df6d/attachment.html>