Configuring IdP to Work With InCommon SAML1 SPs (OhioLink)
bleb1982
btl at fischerinternational.com
Fri Jan 31 11:46:28 EST 2014
I turned IdP logging up to Trace and discovered this in the log. When its
trying to grab the attributes when the attribute query comes back it seems
that the filter, search dn is null.
Any ideas?
07:50:22.392 - DEBUG
[edu.internet2.middleware.shibboleth.idp.profile.saml1.AbstractSAML1ProfileHandler:547]
- Resolving principal name for subject of SAML request from relying party
'https://proxy.ohiolink.edu/shibboleth'
07:50:22.392 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:207]
- Resolving principal name from name identifier of format:
urn:mace:shibboleth:1.0:nameIdentifier
07:50:22.392 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:228]
- Using principal connector shibTransient to resolve principal name.
07:50:22.393 - DEBUG
[edu.internet2.middleware.shibboleth.idp.profile.saml1.AbstractSAML1ProfileHandler:477]
- Resolving attributes for principal 'pamccain' for SAML request from
relying party 'https://proxy.ohiolink.edu/shibboleth'
07:50:22.393 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:125]
- shibboleth.AttributeResolver resolving attributes for principal pamccain
07:50:22.393 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:281]
- Specific attributes for principal pamccain were not requested, resolving
all attributes.
07:50:22.393 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:320]
- Resolving attribute uid for principal pamccain
07:50:22.393 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:360]
- Resolving data connector Fisc_Shib_LDAP for principal pamccain
07:50:22.393 - TRACE
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.dataConnector.TemplateEngine:114]
- Populating velocity context
07:50:22.393 - TRACE
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.dataConnector.TemplateEngine:88]
- Populating the following shibboleth.resolver.dc.Fisc_Shib_LDAP template
07:50:22.394 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.dataConnector.LdapDataConnector:340]
- Search filter: null
07:50:22.394 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.dataConnector.LdapDataConnector:351]
- Performing LDAP read. DN:null
07:50:22.394 - DEBUG
[edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.dataConnector.LdapDataConnector:441]
- LDAP data connector Fisc_Shib_LDAP - Retrieving attributes from LDAP
--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Configuring-IdP-to-Work-With-InCommon-SAML1-SPs-OhioLink-tp7594414p7594503.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.
More information about the users
mailing list