Now I got it!. Thanks! Also I noticed that in secpolicy scenario2, if we change the user name in the client policy, the SOAP message will not send (because the password is not there). So I wonder is it the case or should the SOAP message be sent and invalidated at the service side?. I think this is because the client and the server both uses the same callback function and and the users cannot give user name and password at runtime.
On Jan 29, 2008 3:05 PM, Kaushalye Kapuruge <[EMAIL PROTECTED]> wrote: > Hi, > Your approach is wrong. The http_auth_info is not something related to > username tokens. > You have to create a new struct called rampart_config and give it to the > svc_client as an axis2_options. > Please refer the last comment in here[1] for more information. > Cheers, > Kaushalye > > [1]https://issues.apache.org/jira/browse/RAMPARTC-56?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562482#action_12562482 > > Prasadcse Perera wrote: > > Hi, > > I'm trying to create the user name token with the user name and the > password > > given at the runtime using the function > axis2_options_set_http_auth_info. I > > have set the user inputs to the axis2_option object using the function > > before setting the options to svc client. But the generated SOAP message > > still has the user name defined in client-policy file. Do I have to make > any > > other changes than that?. > > > > > > > -- > http://blog.kaushalye.org/ > http://wso2.org/ > >
