Issue with attribute release consent

[Darren Boss]

I have logging increased to debug for consent and can see the logs now.

I am currently getting prompted for consent in both Firefox and Chrome when I know I've already consented to the SP I'm currently testing with. If I look at the logs, this is what I see:
DEBUG [net.shibboleth.idp.consent.flow.impl.InitializeConsentContext:47] - Profile Action InitializeConsentContext: Created consent context 'ConsentContext{previousConsents={}, chosenConsents={}}'
DEBUG [net.shibboleth.idp.consent.flow.ar.impl.InitializeAttributeReleaseContext:47] - Profile Action InitializeAttributeReleaseContext: Created attribute release context 'AttributeReleaseContext{consentableAttributes={}}'
DEBUG [net.shibboleth.idp.consent.flow.ar.impl.AbstractAttributeReleaseAction:152] - Profile Action PopulateAttributeReleaseContext: Found attributeContext 'net.shibboleth.idp.attribute.context.AttributeContext at 3abc855b'
DEBUG [net.shibboleth.idp.consent.flow.ar.impl.PopulateAttributeReleaseContext:98] - Profile Action PopulateAttributeReleaseContext: Consentable attribute IDs '[eduPersonPrincipalName, givenName, sn, sshPublicKey]'
DEBUG [net.shibboleth.idp.consent.logic.impl.FlowIdLookupFunction:69] - Current flow id is 'intercept/attribute-release'
DEBUG [net.shibboleth.idp.consent.logic.impl.JoinFunction:81] - Result 'dboss:https://oidctest.mit.c3.ca/shibboleth'
DEBUG [net.shibboleth.idp.consent.flow.storage.impl.ReadConsentFromStorage:53] - Profile Action ReadConsentFromStorage: Read storage record 'null' with context 'intercept/attribute-release' and key 'dboss:https://oidctest.mit.c3.ca/shibboleth'
DEBUG [net.shibboleth.idp.consent.flow.storage.impl.ReadConsentFromStorage:57] - Profile Action ReadConsentFromStorage: No storage record for context 'intercept/attribute-release' and key 'dboss:https://oidctest.mit.c3.ca/shibboleth'
DEBUG [net.shibboleth.idp.consent.logic.impl.FlowIdLookupFunction:69] - Current flow id is 'intercept/attribute-release'
DEBUG [net.shibboleth.idp.consent.flow.storage.impl.ReadConsentFromStorage:53] - Profile Action ReadConsentFromStorage: Read storage record 'null' with context 'intercept/attribute-release' and key 'dboss'
DEBUG [net.shibboleth.idp.consent.flow.storage.impl.ReadConsentFromStorage:57] - Profile Action ReadConsentFromStorage: No storage record for context 'intercept/attribute-release' and key 'dboss'
DEBUG [net.shibboleth.idp.consent.flow.impl.PopulateConsentContext:64] - Profile Action PopulateConsentContext: Populating consents: [eduPersonPrincipalName, givenName, sn, sshPublicKey]
DEBUG [net.shibboleth.idp.consent.logic.impl.IsConsentRequiredPredicate:107] - Consent is required, no previous consents

If I open dev console on the browser and look at local storage, I see shib_idp_session_ss and shb_idp_persistent_ss with what appears to be a base64 encoded value. I see in the logs that it cannot locate the previous consent.
No storage record for context 'intercept/attribute-release' and key 'dboss:https://oidctest.mit.c3.ca/shibboleth'

It was fine while testing yesterday until the evening when it started prompting again. I haven't tweaked any setting related to the lifetime of local storage. This seems consistent with some some other staff were reporting to me, doesn't prompt for some period of time, seems to be about a day and then prompts again.

In the dev console I can type localStorage.getItem("shib_idp_persistent_ss"); and it returns this string. What do I need to do to decode and possibly decrypt this string to see what the issue with local storage might be?
>> What can I do to debug this issue further?
>

>Increase logging to debug for net.shibboleth.idp.consent.
>

>Idea is to prompt for consent if the attributes being released have changed, but not otherwise.>
>

>Tom