Hi Werner; I know Policy is still half way done. I doing some work regarding Axis2 policy implementation and asked to know the current status. Myself and Ruchith will be discussing this I will get back to you on this.
Let me add a thought? what happens if there is a policy assertion(which fell under WS-Security Policy NS) which is not identified by the WSS4J policy processor and there are more assertions that are identified. Right now as far as I know WSS4J reject the all the policy assertions if this happens It is possible that users security solution consists of WSS4J together with a custom authorization solution and Policy that WSS4J do not understood is intended to authorization module. (Actually the scenario is not hypothetical and I am trying to solve this problem in a scenario involve capability tokens) In axis2 policy processing we allow multiple modules to bind to same policy name space. How do you think this should be handled in terms of WSS4J? Thanks Srinath On 3/3/06, Dittmann, Werner <[EMAIL PROTECTED]> wrote: > All, > > the support of WS SecurityPolicy (WSP) is not yet available in WSS4J. > First of all the WSP spec itself is not yet stable and needs some > more clarification to become usable in a praticable manner. This is > an ongoing activity at the OASIS WS-SX TC. > > In anticipation of WSP support we refactored parts of the WSS4J code. > This refactoring is not yet complete, expect another 2-4 weeks before > that is done (including the tests). This refactoring implies new > interfaces and modifications to the WSS4J Axis/JAX-RPC handler (no > structural modifications, just new classes and some some parameter > changes). > > After this refactoring is done and we have the same functional > level as today we can start with the real WSP support. At that point > in time we need the policy information that a WSDL contains and > process it(a WSDL may contain policies at several points and these > policies have to be merged to form one policy for a specific message). > Policy processing would include several steps: > > - parsing the policy and set-up of an internal data structure that > refelects the policy > > - using this data plus some additional configuration data a new module > which is part of the Axis/JAX-RPC handlers can create the message. > > Having said that: pls allow some more time until we can bring in real > policy support into WSS4J and the associated handlers. > > > > -----Ursprüngliche Nachricht----- > > Von: Srinath Perera [mailto:[EMAIL PROTECTED] > > Gesendet: Donnerstag, 2. März 2006 21:35 > > An: [email protected] > > Cc: [email protected] > > Betreff: [Axis2]Level of Policy Support at WSS4J > > > > Hi All; > > > > Right now, when a module is engaged with a AxisService that has policy > > descriptions the Module.engageNotify() -> > > WSSPolicyProcessor.processPolicy() called and the code try to process > > the policy. > > > > What are the level of support from the WSSPolicyProcessor? and what > > are the limitations and TODOs? any room to help? > > > > Srinath > > -- > > ============================ > > Srinath Perera: > > http://www.cs.indiana.edu/~hperera/ > > http://www.bloglines.com/blog/hemapani > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- ============================ Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani
