employeeNumber attribute

[Christopher J. Bottaro]

I turned the log level to debug.  Below is (what I think is) the relevant
snippet:

2012-09-11 17:25:38 DEBUG Shibboleth.SSO.SAML2 [2]: SSO profile processing
completed successfully
2012-09-11 17:25:38 DEBUG Shibboleth.SSO.SAML2 [2]: extracting pushed
attributes...
2012-09-11 17:25:38 DEBUG Shibboleth.AttributeExtractor.XML [2]: skipping
unmapped NameID with format
(urn:oasis:names:tc:SAML:2.0:nameid-format:transient)
2012-09-11 17:25:38 INFO Shibboleth.AttributeExtractor.XML [2]: skipping
unmapped SAML 2.0 Attribute with Name: urn:oid:0.9.2342.19200300.100.1.1
2012-09-11 17:25:38 DEBUG Shibboleth.SSO.SAML2 [2]: resolving attributes...
2012-09-11 17:25:38 DEBUG Shibboleth.AttributeResolver.Query [2]: found
AttributeStatement in input to new session, skipping query
2012-09-11 17:25:38 DEBUG Shibboleth.SessionCache [2]: creating new session
2012-09-11 17:25:38 DEBUG Shibboleth.SessionCache [2]: storing new
session...

So it looks like they are pushing NameID, which we are not setup to
receive.  That's fine I guess.

Curious though, I don't see anywhere in the log where they are pushing
attributes that we *are* accepting.

Also, employeeNumber is nowhere to be seen in the logs.

Any ideas?  Thanks for the help.

On Tue, Sep 11, 2012 at 8:37 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 9/10/12 11:46 PM, "Nate Klingenstein" <ndk at internet2.edu> wrote:
> >
> >The easiest thing to do is probably to look at the incoming assertion
> >(it'll be in your shibd.log if you have it turned to DEBUG).  You'll want
> >to check for the employeeNumber attribute in there.  If it's present,
> >then make sure that the attribute's name
> > matches what your attribute-map.xml expects.
>
> Even without that, every attribute that's unmapped and skipped is logged
> anyway.
>
> -- Scott
>
>
> --
> 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/20120911/a1ca33a6/attachment.html