[wsf-c-dev] [Fwd: Re: [wsf-php-user] Does WSF/PHP support Rampart 1.4?]
Samisa Abeysinghe
samisa at wso2.com
Tue Jul 15 21:54:14 PDT 2008
Have we done an interop test with Rapmart 1.4?
Samisa...
-------- Original Message --------
Subject: Re: [wsf-php-user] Does WSF/PHP support Rampart 1.4?
Date: Tue, 15 Jul 2008 22:09:38 +0530
From: Manjula Peiris <manjula at wso2.com>
Reply-To: wsf-php-user at wso2.org
To: wsf-php-user at wso2.org
References:
<EMEW-k6ECFV9c4a0e783d8fbec9e6ab5bed65468fdc-88493EDAE8A32D4EA88F17102879E395082FE881 at moonraker.campus.ncl.ac.uk>
<EMEW-k6ECVb0c6d487e803cba84aa04f08336028cbf-1216121525.6024.53.camel at manjula>
<EMEW-k6EClZc6658e19c480adf26b95b8dfaca97699-88493EDAE8A32D4EA88F17102879E395082FE882 at moonraker.campus.ncl.ac.uk>
Sanjay,
Following things may be causing the error.
1. Try enabling WS Addressing in client script.
2. Check whether the usernames and passwords are correct.
3. Try sending password as plainText.
If none of this work try sending this message through https. Else send
us the log file of your server.
Thanks,
-Manjula.
On Tue, 2008-07-15 at 12:47 +0100, Sanjay Vivek wrote:
> Hi Manjula,
>
> I've attached the policies for both the service and the client. I've
> also attached the client PHP script for your reference. The SOAP request
> and response messages is given below. Cheers.
>
> Regards
> Sanjay
>
> ### SOAP request ###
>
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header>
> <wsse:Security soapenv:mustUnderstand="1"
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse
> curity-secext-1.0.xsd">
> <wsu:Timestamp
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
> urity-utility-1.0.xsd">
> <wsu:Created>2008-07-15T10:28:12.022Z</wsu:Created>
> <wsu:Expires>2008-07-15T10:33:12.022Z</wsu:Expires>
> </wsu:Timestamp>
> <wsse:UsernameToken
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
> urity-utility-1.0.xsd">
> <wsse:Username>GrouperSystem</wsse:Username>
> <wsse:Password
> Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-t
> oken-profile-1.0#PasswordDigest">Hexfq7B1ts699hZkymdgE+0DuZY=</wsse:Pass
> word>
> <wsse:Nonce>esMzag5uyTyXBTAQaKXzOaYOqlIt19Fv</wsse:Nonce>
> <wsu:Created>2008-07-15T10:28:12.022Z</wsu:Created>
> </wsse:UsernameToken>
> </wsse:Security>
> </soapenv:Header>
> <soapenv:Body>
> <ns1:getMembersLite
> xmlns:ns1="http://soap.ws.grouper.middleware.internet2.edu/xsd">
> <ns1:param0>v1_3_000</ns1:param0>
>
> <ns1:param1/>
>
> <ns1:param2/>
>
> <ns1:param3>All</ns1:param3>
>
> <ns1:param4/>
>
> <ns1:param5/>
>
> <ns1:param6/>
>
> <ns1:param7/>
>
> <ns1:param8/>
>
> <ns1:param9/>
>
> <ns1:param10/>
> </ns1:getMembersLite>
> </soapenv:Body></soapenv:Envelope>
>
>
> ### SOAP response ###
>
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Receiver</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text
> xml:lang="en-US">InvalidSecurity</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail />
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
> >-----Original Message-----
> >From: wsf-php-user-bounces at wso2.org
> >[mailto:wsf-php-user-bounces at wso2.org] On Behalf Of Manjula Peiris
> >Sent: 15 July 2008 12:32
> >To: wsf-php-user at wso2.org
> >Subject: Re: [wsf-php-user] Does WSF/PHP support Rampart 1.4?
> >
> >On Tue, 2008-07-15 at 12:15 +0100, Sanjay Vivek wrote:
> >> Hi all,
> >>
> >> Is WSF/PHP compatible with Rampart 1.4? I've a PHP client based on
> >> WSF/PHP and it was working fine until I tried to invoke a newly
> >> Rampart
> >> 1.4 enabled service. My previous service was Rampart 1.3 enabled.
> >>
> >> I keep getting a "Invalid Security" error whenever I to try
> >to invoke
> >> the Rampart 1.4 enabled service so just wondering if WSF/PHP
> >supports
> >> Rampart 1.4? Cheers.
> >
> >It should support, because both of them communicate through
> >SOAP and according to WS-Security. So further dig in to the
> >problem can you send us the following, 1. The Messages from
> >WSF/PHP 2. The policies at both client and server 3. The
> >Client PHP script.
> >
> >Thanks,
> >-Manjula
> >
> >
> >
> >
> >>
> >> Regards
> >> --------------
> >> Sanjay Vivek
> >> Web Analyst
> >> Middleware Team
> >> ISS
> >> Newcastle University
> >>
> >> _______________________________________________
> >> Wsf-php-user mailing list
> >> Wsf-php-user at wso2.org
> >> http://wso2.org/cgi-bin/mailman/listinfo/wsf-php-user
> >
> >
> >_______________________________________________
> >Wsf-php-user mailing list
> >Wsf-php-user at wso2.org
> >http://wso2.org/cgi-bin/mailman/listinfo/wsf-php-user
> >
> _______________________________________________
> Wsf-php-user mailing list
> Wsf-php-user at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsf-php-user
_______________________________________________
Wsf-php-user mailing list
Wsf-php-user at wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/wsf-php-user
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.4.10/1552 - Release Date: 7/14/2008 6:28 PM
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
More information about the Wsf-c-dev
mailing list