Attribute consent display logic is still confusing

Tom Zeller tzeller at dragonacea.biz
Mon Nov 30 13:21:36 EST 2015


> On Nov 27, 2015, at 3:55 AM, Etienne Dysli-Metref <etienne.dysli-metref at switch.ch> wrote:
> 
> <bean class="ch.SWITCH.aai.uApprove.ar.AttributeProcessor"
>      p:blacklist="${ar.attributes.blacklist}"
>      p:order="${ar.attributes.order}"/>
> 
> So apparently, uApprove has no notion of a whitelist and always applies
> the blacklist before sorting attributes.

Looking back, it seemed reasonable to think of the ‘order’ list as the whitelist counterpart to the blacklist, and then I re-used the whitelist / blacklist / regex implementation from ValidateRemoteUser and conf/authn/remoteuser-internal-authn-config.xml. Perhaps multiple mistakes on my part, I’ll need to think about how to fix it.

Thanks for pointing this out,
Apologies,
Tom




More information about the users mailing list