skipping unmapped SAML 2.0 Attribute with Name: urn:oid:0.9.2342.19200300.100.1.3

[Brian Tingle]

I was using the shibboleth-sp-2.4.3 package from pkgsrc on my first app.

I see 2.4.3 is no longer secure, so I've set up my second app using SP 2.5.2.

As far as I can tell, my new app and my old app have equivalent configurations.  I had to add in some attributes to shibboleth2.xml for 2.5.2 to get rid of some warnings form shibd -t, but everything else is the same except for the entityId as far as I can tell.

On my first app (2.4.3) I'm able to get both the attributes I want.

On my second app (2.5.2) I'm only able to get one of the attributes I want.

My IdP is sending equivalent SAML that includes both the attributes I want.

The second app on 2.5.2 says this in the logs

skipping unmapped SAML 2.0 Attribute with Name: urn:oid:0.9.2342.19200300.100.1.3

The first app using 2.4.3 gives me this

decoding SimpleAttribute (mail) from SAML 2 Attribute (urn:oid:0.9.2342.19200300.100.1.3) with 1 value(s)

I'm also only seeing these in the second app's logs
unable to extract attributes, unknown XML object type: saml2p:Response
unable to extract attributes, unknown XML object type: saml2:AuthnStatement

This gist shows more of the debug log around these messages with the new and the old SP
https://gist.github.com/tingletech/6109136

Does anyone have any thoughts or suggestions on this issue?  I'm stumped.

Thanks -- Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130730/748626cb/attachment-0001.html