Ok. Please be aware there is an errata associated with the authorization elements. http://www.osoa.org/jira/browse/POLICY-26
On Wed, Mar 5, 2008 at 1:51 AM, Venkata Krishnan <[EMAIL PROTECTED]> wrote: > +1. I will start looking into this after I am done with some > half-finished > things on my plate at the moment. Thanks. > > - Venkat > > On Wed, Mar 5, 2008 at 12:00 PM, Jean-Sebastien Delfino < > [EMAIL PROTECTED]> wrote: > > > Greg Dritschler wrote: > > > Is the authentication policy going to bear any resemblance to the > policy > > > described in section 1.7.3.1 of the Policy spec, or is it completely > > > different? > > > > > > Greg > > > > > > > I think that Tuscany should implement the authorization - I guess that's > > what you meant :) - and security identity policies as described in > > section 1.7.3.1 of the Policy spec, at least. > > > > We could start with just implementing the model and XML reading for the > > elements described in 1.7.3.1 and let the various component > > implementation extensions handle them (or not) in their own way, but > > having the model and XML processors would be a good start IMO. > > > > Any thoughts? > > -- > > Jean-Sebastien > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
