Consent Preferences Not Stored
Cantor, Scott
cantor.2 at osu.edu
Tue Apr 18 15:06:30 EDT 2017
> I'm trying to troubleshoot a problem with storing consent preferences using
> HTML 5 local storage, and not making much progress. I turned up the logs to
> DEBUG for the flow and client storage components, and the
> ClientStorageService output is conspicuously missing:
It looks more like the consent flow itself didn't produce a result to store.
> 2017-04-18 14:27:01,347 DEBUG
> net.shibboleth.idp.consent.flow.ar.impl.ReleaseAttributes:96
> 2001:468:c80:2103:b84c:c820:f134:979f Profile Action ReleaseAttributes: Not
> releasing attributes '{}'
Is that a bug in the log line or signifying something about it not releasing any attributes?
> 2017-04-18 14:27:01,348 DEBUG
> net.shibboleth.idp.profile.interceptor.impl.WriteProfileInterceptorResultToS
> torage:68 2001:468:c80:2103:b84c:c820:f134:979f Profile Action
> WriteProfileInterceptorResultToStorage: No results available from
> interceptor context, nothing to store
That's indicating it has nothing to record, independent of the actual storage service used.
> This feels like a dumb configuration mistake, but I just don't see it. I have
> what I believe is configuration specifying HTML5 local storage in
> idp.properties:
>
> # Set to "shibboleth.StorageService" for server-side storage of user consent
> idp.consent.StorageService = shibboleth.ClientPersistentStorageService
That enables client-side, there's a separate property to turn on local storage. The consent flow can still write to cookies, in limited fashion, so that isn't really itself any answer, I think the issue is the flow itself.
-- Scott
More information about the users
mailing list