attribute filter RuleReference ?

[Rod Widdowson]

The longest time spent so far in doing AttributeRuleReference (as well as
its brothers Permit and Deny) was spent in working out that it didn't work
in V2.

AFAIR most of the code is there, in skeletal form, and a small test
(policy4.xml) so 'all' we need to do is to

1) Clarify where to get the reference from
   a) Grab the reference from the body test - which is what the code
currently does.
   b) Grab the reference from "ref" as suggested by the schema
   c) Both with a preference for (b) (my suggestion)
2) Make this so (I suggest a base class which implements the decision so we
can change our minds)
3) Optionally update the schema
4) Update the documentation

My estimate is that the coding is sub half a day (once whoever does it is up
to speed).

/r

> -----Original Message-----
> From: dev-bounces at shibboleth.net [mailto:dev-bounces at shibboleth.net]
> On Behalf Of Cantor, Scott
> Sent: 10 July 2013 22:06
> To: Shib Dev
> Subject: Re: attribute filter RuleReference ?
> 
> 
> 
> On 7/10/13 4:51 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
> 
> >Should we remove RuleReference from the attribute filter schema or
> >leave RuleReference unimplemented as in IdPv2 or should we implement
> >it for IdPv3 ?
> 
> I think it's down to time to implement. If it were a couple of hours time
> to get it done, I would say just do it. If it's a day or more work, I
> would defer it as an open item and at ship time assess and have either
> closed it or remove the elements from the schema.
> 
> -- Scott
> 
> 
> --
> To unsubscribe from this list send an email to dev-
> unsubscribe at shibboleth.net