users Digest, Vol 25, Issue 134

[Nate Klingenstein]

I should add, double-check to make sure you have:

11:57:48.650 - DEBUG [edu.internet2.middleware.shibboleth.common.attribute.provider.ShibbolethSAML2AttributeAuthority:247] - Encoded attribute uid with encoder of type edu.internet2.middleware.shibboleth.common.attribute.encoding.provider.SAML2StringAttributeEncoder

in the IdP logs, and look for the uid in the assertion that follows just to be sure.

      <saml2:Attribute FriendlyName="uid" Name="urn:oid:0.9.2342.19200300.100.1.1" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
         <saml2:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">superego</saml2:AttributeValue>
      </saml2:Attribute>

On Jul 30, 2013, at 18:08 , Nate Klingenstein wrote:

> Gilles,
> 
>> 16:24:52.727 - DEBUG [edu.internet2.middleware.shibboleth.common.attribute.filtering.provider.ShibbolethAttributeFilteringEngine:114] - Filtered attributes for principal yoyo.  The following attributes remain: [uid, surname, givenName, commonName, transientId, email, telephoneNumber, mobileNumber]
> 
> So, it looks like uid is present and the IdP is releasing it.  The next thing to check is whether the SP is receiving it and dropping it because there is no mapping or there is some policy check being failed.  The SP logs will give you the information here; as far as the IdP is concerned, assuming you're using the default encoders, all is well.
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>