> well, you COULD call a new filter instance...from a policy.
Ok. If that works, that's fine... But even then the attribute filter file is keyed off the realm for pre- and post-proxy.
> 'as standard' means in the main release... i'm not sure about that. I'd go with the 'enable
> it is you want it' approach.
Well, if you're enabling attribute filters, then by default this means the attributes for the APC are correctly filtered (i.e. left alone).
> attr_filter_moonshot:
[snip]
> or some such (the access_challenge one is interesting...it really should be a very small
> subset..so we could/should(?) keep the default and not call it here.....
If it is drop-in, yes, then that's fine. The point after all is that this *should* be easy to enable Moonshot. As it stands, if you stray off the standard path (i.e. dead stock config, no messin'), it all goes pear-shaped quickly and we should do our best to avoid it going pearshaped.
Stefan
Janet(UK) is a trading name of Jisc Collections and Janet Limited, a
not-for-profit company which is registered in England under No. 2881024
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238
|