Legacy Issue Number: 3257
Source: 2AB ( Bob Burt)
The DynamicAttributeService was designed to allow modification of
SecAttributes prior to locating and using PolicyEvaluators. These
modifications are application are most likely specific in nature.
Unfortunately the entire service can only have one DynamicAttributeService,
therefore, instance of RAD service have to be partitioned for different
applications. It might have been better to have associations with
ResouceNames such as was done with PolicyEvaluators. Another alternative
might have been to associate a DynamicAttributeService with a combinator,
since different resource names can use different combinators this implies
they also could then have different DynamicAttributeServices. This is
probably not an important issue, but it can dictate how applications must
deploy instances of the service.
Reported: RAD 1.0b1 — Wed, 26 Jan 2000 05:00 GMT
Disposition: Resolved — RAD 1.0
Close this issue with no change.
Updated: Fri, 6 Mar 2015 23:14 GMT