Shibboleth support in my application

[Paul Hethmon]

Right, but that is the resolver step. So the IdP got the data from LDAP.
You need to check the logs and see if your filter policy actually released
them (it won't unless you tell it to). Then check the SP side and see if
it got them and made them available to your application.

Paul

On 9/17/13 8:40 AM, "mmichaelchn" <mmichaelchn at gmail.com> wrote:

>Sorry, I forgot to mention that they are actually coming in the idp log
>file.
>
>16:58:06.436 - DEBUG
>[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.da
>taConnector.LdapDataConnector:414]
>- LDAP data connector myldapdc - Found the following attribute: pager[+1
>779
>041 6341]
>16:58:06.437 - DEBUG
>[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.da
>taConnector.LdapDataConnector:414]
>- LDAP data connector myldapdc - Found the following attribute:
>uid[user.0]
>16:58:06.437 - DEBUG
>[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.da
>taConnector.LdapDataConnector:414]
>- LDAP data connector myldapdc - Found the following attribute:
>mail[user.0 at maildomain.net]
>