[wsf-c-dev][WSF-PHP] Using security policy in WSF-PHP

[Manjula Peiris]

Hi,

The main idea of attaching policies at these different levels is to
support policy processing in different attaching points in WSDL. So when
we have full WSDL support setting policies at these different levels
will not be complex. The other thing is even though we give support for
these messgae level policy attaching as client options, most of the
users will set policies at service level. I think in Axis2/Java also for
samples policy setting is done at services level. So we can give the
message level policy attaching support, but for samples we may strict to
service level policy attaching so the users will not feel complicated.
For advanced users we can document it.

-Manjula.
 


On Mon, 2007-06-04 at 16:07 +0530, Kaushalye Kapuruge wrote:
> Hi,
> For me this is not "that" complicated as you've mentioned in your 
> mail.   Besides we have to support these levels. PHP gurus may raise  
> their voice here. :) It's better if you can show the interface to create 
> these policy objects as well.
> Cheers,
> Kau
> 
> Buddhika Semasinghe wrote:
> > Hi ;
> >
> >  We have to change some security stuffs in WSF-PHP since neethi is 
> > introduced to AXIS2C.Earlier we did not have a mechanism to set 
> > service-level policy, operation-level policy and message-level policy. 
> > To do that we have to add some options to our current API. In server 
> > side we can introduce another option to our options array as
> > "policy " => operation_name  and
> > operation_name => policy object | array of options
> >
> >
> > 1.For service-level policy we can use the same technique as;
> >
> >     $svr = new WSService(array("operations" => $operations,
> >                                                "policy" => $policy,
> >                                                "securityToken" => 
> > $sec_token));
> >
> >
> >
> > 2.For both service-level and operation-level we can do
> >
> >    $svr = new WSService("operations" => $operations,
> >                                     "policy" => $policy_obj1,
> >                                      "securityToken" => $sec,
> >                                      "op_policy "=> $oppolicy);
> >                              
> >    $oppolicy  = array("add" => $policy_obj2,
> >                               "div" => $policy_obj3);
> >                                                                     
> > 3.For service-level, operation-level and message-level policies
> >  
> >    $oppolicy  = array("add" => array( "policy" =>$policy_obj2,
> >                                                         "in" => 
> > $policy_obj3,
> >                                                         "out" => 
> > $policy_obj4));
> >    Here if we omit policy option, no operation-policy is present only 
> > service-level and message-level policies.
> >
> >
> >     Seems it is getting more complicated for the user :-( . I would 
> > like to have your comments?
> >
> >
> >
> > thanks
> > Buddhika
> >
> > ~                                                                                
> >
> >
> > _______________________________________________
> > Wsf-c-dev mailing list
> > Wsf-c-dev at wso2.org
> > http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev
> >
> 
> 
> _______________________________________________
> Wsf-c-dev mailing list
> Wsf-c-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev