Attribute release consent failing (sometimes)

[Manuel Haim]

Thanks Tom,

> If you set the log level of
> net.shibboleth.idp.consent.flow.impl.ExtractConsent to DEBUG, you
> should see the attribute ids returned from the browser, as well as
> whether isApproved is true or false. That should help determine if the
> browser is the culprit (if you see isApproved=false instead of
> isApproved=true).

I have added the following line to my idp.properties and will keep an
eye on the logs:

net.shibboleth.idp.consent.flow.impl.ExtractConsent=DEBUG

By the way, removing the "checked" attribute from the hidden input
within attribute-release.vm template didn't help yet.


> Looks like idp.consent.compareValues is true (otherwise values are not
> stored in consent storage records).

Yes, idp.consent.compareValues=true is also set, as users should be
asked again for their consent on attribute changes.

Kind regards,
Manuel