idp.consent.userStorageKeyAttribute attribute not available when consent flow runs

[Cantor, Scott]

On 7/7/15, 11:34 AM, "users on behalf of Etienne Dysli-Metref" <users-bounces at shibboleth.net on behalf of etienne.dysli-metref at switch.ch> wrote:

>The attribute configured here
>"swissEduPersonUniqueID.withoutAttributeEncoder" is an encoder-less
>version of the swissEduPersonUniqueID so it won't be released. Now the
>questions: must the attribute used by consent flow storage
>(idp.consent.userStorageKeyAttribute property) be 1) encoded 2) released
>by filtering? or is it subject to other prerequisites in order to be
>available in consent flows?

The idea behind the unencoded attribute defs is so you can release them "harmlessly" because they won't ever actually show up in SAML. So for now, releasing them is necessary, pending the fix to this in 3.2 to start allowing these kinds of subsystems to read from the unfiltered set.

-- scott