SP: Assertion contains an unacceptable AudienceRestriction
Scott Gerlach
sgerlach at gmail.com
Fri Aug 14 16:58:48 EDT 2015
> >In fact it's not just the request issuer entityID that's different, it's
> other things like the request Destination and ACS URL. Were you
> deliberately obfuscating all of that in what you've been posting?
>
I was, and failed miserably ultimately :$ (encoding/deflate got me on that
one, I knew that was gonna happen...). The replaced strings are
find/replace for actual servername, acs url, and destination and not hand
replaced. I have closely checked the request and responses and they are not
mispelled or mis-capitalized. I did turn off the Audience policy
<PolicyRule type="Conditions">
<!--<PolicyRule type="Audience"/>-->
<!-- Enable Delegation rule to permit delegated access. -->
<!-- <PolicyRule type="Delegation"/> -->
</PolicyRule>
and now am getting this error
2015-08-14 13:29:16 ERROR Shibboleth.Listener [4195] shib_check_user:
remoted message returned an error: AudienceRestriction condition not
successfully validated by policy.
2015-08-14 13:29:16 ERROR Shibboleth.Apache [4195] shib_check_user:
AudienceRestriction condition not successfully validated by policy.
which is different, but not better. I guess
again many thanks for the help here
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150814/05112092/attachment-0001.html>
More information about the users
mailing list