Consent Logging

[Jeffrey Crawford]

It looks as though the plumbing explained by Tom is in place. However I'm
not sure if that means it is supposed to work or if I'm supposed to change
something to have it actually logged. Does logback need to be updated to
"Make it so"?

In short, it's not working now, even though the fields are in place.

Jeffrey
​ C.​
<jeffreyc at ucsc.edu>

Both pilots and IT professionals require training and currency before
charging into clouds!
---------------------------------------

On Thu, Mar 3, 2016 at 1:04 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > It should be logged. Looking at views/intercept/attribute-release.vm, the
> > button to deny is named “_eventId_AttributeReleaseRejected”. The
> > AttributeReleaseRejected event is mapped to a local error in
> conf/errors.xml
>
> That doesn't impact whether it would be logged in your consent audit log,
> though, that would have to be explicit in the flow.
>
> It would cause the overall audit result to include that Event (I think),
> though the Event field isn't in the audit record by default.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160303/c35bab72/attachment.html>