missing attributes in output from idpv3 /cas/serviceValidate

[Tom Zeller]

> The one weird thing is that that after finding the matching relying party:
> 
> 2016-04-04 10:33:48,516 - DEBUG [net.shibboleth.idp.cas.service.PatternServiceRegistry:85] - Evaluating whether https://login.proxy-dev.library.cpp.edu/login?qurl=ezp.2aHR0cHM6Ly9sb2dpbi5wcm94eS1kZXYubGlicmFyeS5jcHAuZWR1L215Z3JvdXBz matches https?://(login\.)?proxy(-dev)?\.library\.cpp\.edu/login.*
> 2016-04-04 10:33:48,517 - DEBUG [net.shibboleth.idp.cas.service.PatternServiceRegistry:87] - Found match
> 2016-04-04 10:33:48,517 - DEBUG [net.shibboleth.idp.cas.flow.impl.BuildRelyingPartyContextAction:81] - Setting up RP context for verified relying party https://login.proxy-dev.library.cpp.edu/login?qurl=ezp.2aHR0cHM6Ly9sb2dpbi5wcm94eS1kZXYubGlicmFyeS5jcHAuZWR1L215Z3JvdXBz
> 
> It then says there's no match and it's using the default?
> 
> 2016-04-04 10:33:48,517 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:293] - Resolving relying party configuration
> 2016-04-04 10:33:48,517 - DEBUG [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:314] - No relying party configurations are applicable, returning the default configuration shibboleth.DefaultRelyingParty

That’s expected unless you have relying party overrides (configured via ‘shibboleth.RelyingPartyOverrides’) which match.

> Any thoughts on why the attributes aren't showing up?

Are any attributes logged to idp-audit.log for serviceValidate ?