Missing attribute from SAML2 response

David Bantz dabantz at alaska.edu
Wed Nov 7 12:00:27 EST 2012

Prior to the block of encrypted data in the logs should be something like 'SAML assertion to be encrypted:'
with the clear-text SAML assertion.  You'll likely find nothing in that assertion for the missing
atribute, confirming a prior problem in setting the value - such as retrieving no acceptable value
from the data source or failing to encode it.

David Bantz

On Tue, 6 Nov 2012, at 11:09 , mjoen <marion.nalepa at proquest.com> wrote:

> I am running an SP server and it receives a response that includes an
> affiliation (allegedly), but the affiliation is not coming through after the
> response is parsed. I'm getting:
> WARN Shibboleth.AttributeDecoder.NameID [4]: AttributeValue was not of a
> supported type and contains no child elements
> I'm not sure how to debug this further. Nothing I try shows me the attribute
> values coming through. I can turn on DEBUG level logging, but the relevant
> fields are in a big CipherData block that doesn't seem to show up anywhere
> unencrypted (at least with anything I've tried).
> Running Shibboleth SP version 2.4.2
> --
> View this message in context: http://shibboleth.1660669.n2.nabble.com/Missing-attribute-from-SAML2-response-tp7583010.html
> Sent from the Shibboleth - Users mailing list archive at Nabble.com.
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

More information about the users mailing list