IdP Consent: Different storage key bases for "Terms of Use" and "Attribute Release" consent flows

[Cantor, Scott]

On 9/13/17, 1:10 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:

> > Or is there a simple way to configure an alternative bean "shibboleth.consent.UserStorageKey"
> > for the "intercept/attribute-release" flow without modifying the system configuration
> > (i.e. system/flows/intercept/attribute-resolver.xml), e.g. by defining an overriding
> > bean somewhere?
>
> I hope it is that simple.

With a system change it's a simple matter to add the additional property and back off to the old one, but I don't think there's any real way otherwise.

However, I believe the bean is a Function<ProfileRequestContext> ? I suspect with enough screwing around you could build a Function that returned a different value based on which interceptor was running.

That would be the pre-3.4 fix I imagine but once a new property had been defined, you'd probably just make the system change in expectation of it continuing to function later.

-- Scott