missing attributes in output from idpv3 /cas/serviceValidate

[Tom Zeller]

On Wed, Apr 6, 2016 at 11:03 PM, Paul B. Henson <henson at cpp.edu> wrote:
> The login step processed the attribute filter, the serviceValidate step
> did not, and did not call PrepareTicketValidationResponseAction.

Well, PrepareTicketValidationResponseAction logs attributes present in
the attribute context. To determine whether that action/step is
actually being called would require turning up Spring Web Flow
logging.

> So, the samlValidate endpoint has attributes and the serviceValidate does
> not. I'm pretty sure based on this methodology it's clear which logs are
> from which step. It looks like the attribute filter policy isn't getting
> triggered at all during the serviceValidate call? But it is for the
> samlValidate call? What would cause that?

I don't know, but I do know that the samlValidate flow differs from
serviceValidate in that samlValidate always resolves attributes,
whereas serviceValidate is conditional based on a boolean. But I don't
think that's the issue.

> Scott, I hope you don't mind, but I'm going to shoot you these logs
> in their entirety under separate cover.

Send them to me too please if you don't mind. Turning
'org.springframework.webflow' logging up to DEBUG would be helpful to
me.