Filtering attributes problem

[Cantor, Scott]

On 9/11/13 11:08 AM, "Gene Matthews" <gmatthew at hitachi-cta.com> wrote:

>Thanks Scott.
>I added a <resolver:AttributeEncoder.../> section for the attributes in
>question using the OID and they are now showing up.
>
>I have one attribute that I was directed by the SP to change to the
>SAML2StringNameID encoding.

There are certainly many broken SPs, usually ones not running Shibboleth,
that have peculiar requirements for specific NameID content instead of the
flexbility to just map what comes in to what they need.

>  Is there a way for me to verify if that info is being sent since it
>doesn't show up in the assertion?

It's in the assertion, it's not in the resolver testing output.

Turn up logging and you can see what goes out. The best choice is to
operate a dev instance with the same configuration so you can generate
responses with it at full DEBUG logging and verify anything you need to.

-- Scott