You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by Barry McGann <ba...@thb.scot.nhs.uk> on 2006/03/15 10:15:19 UTC
Re: WS-Security UsernameToken Issue (WSS4J-based Java client vs. .NET
server)
What error message are you getting?
Soactive Inc wrote:
> Hi All,
>
> I am trying to access a .NET service with a Java/Axis client (using
> WSS4J) and am getting a security-related error. Here are the details:
>
> * Web Service: on .NET uses WS-Security UsernameToken (with Password
> Digest)
>
> * Request Message
>
> <soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
> http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Header> <wsse:Security xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
> <wsse:UsernameToken xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
> <wsse:Username xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">TestDev</wsse:Username>
> <wsse:Password Type="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest"
> xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">R7bh5dDlYgjCurx6Dwq9ki39lQg=</wsse:Password>
> <wsse:Nonce xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">/tA24bdIc0uwX7euUqvMVQ==</wsse:Nonce>
> <wsu:Created xmlns:wsu="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2006-03-14T22:34:50.971Z</wsu:Created>
> </wsse:UsernameToken> </wsse:Security> </soapenv:Header>
> <soapenv:Body> <ValidateEmail
> xmlns="urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2">
> <Email
> xmlns="urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2">
> testuser@myco.com <ma...@myco.com></Email> </ValidateEmail>
> </soapenv:Body> </soapenv:Envelope>
>
>
> * Response Message
>
> <soapenv:Envelope xmlns:soapenv="
> http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body>
> <soapenv:Fault> <faultcode>soapenv:FailedAuthentication</faultcode>
> <faultstring>The security token could not be authenticated or
> authorized</faultstring> <faultactor>
> http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx</faultactor>
> <detail> <string/> </detail> </soapenv:Fault> </soapenv:Body>
> </soapenv:Envelope>
>
> Any inputs towards appropriately troubleshooting and resolving this
> issue would be appreciated.
>
> Regards.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org
Re: WS-Security UsernameToken Issue (WSS4J-based Java client vs. .NET server)
Posted by Soactive Inc <so...@gmail.com>.
<soapenv:Fault> <faultcode>soapenv:FailedAuthen tication</faultcode>
<faultstring>The security token could not be authenticated or
authorized</faultstring> <faultactor>
http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx</faultactor>
<detail> <string/> </detail> </soapenv:Fault>
On 3/15/06, Barry McGann <ba...@thb.scot.nhs.uk> wrote:
>
> What error message are you getting?
>
>
>
> Soactive Inc wrote:
> > Hi All,
> >
> > I am trying to access a .NET service with a Java/Axis client (using
> > WSS4J) and am getting a security-related error. Here are the details:
> >
> > * Web Service: on .NET uses WS-Security UsernameToken (with Password
> > Digest)
> >
> > * Request Message
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
> > http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> > <soapenv:Header> <wsse:Security xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
> > <wsse:UsernameToken xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
> > <wsse:Username xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">TestDev</wsse:Username>
> > <wsse:Password Type="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest
> "
> > xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">R7bh5dDlYgjCurx6Dwq9ki39lQg=</wsse:Password>
> > <wsse:Nonce xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">/tA24bdIc0uwX7euUqvMVQ==</wsse:Nonce>
> > <wsu:Created xmlns:wsu="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> ">2006-03-14T22:34:50.971Z</wsu:Created>
> > </wsse:UsernameToken> </wsse:Security> </soapenv:Header>
> > <soapenv:Body> <ValidateEmail
> > xmlns="urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2">
> > <Email
> > xmlns="urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2">
> > testuser@myco.com <ma...@myco.com></Email> </ValidateEmail>
> > </soapenv:Body> </soapenv:Envelope>
> >
> >
> > * Response Message
> >
> > <soapenv:Envelope xmlns:soapenv="
> > http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
> > http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body>
> > <soapenv:Fault> <faultcode>soapenv:FailedAuthentication</faultcode>
> > <faultstring>The security token could not be authenticated or
> > authorized</faultstring> <faultactor>
> > http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx
> </faultactor>
> > <detail> <string/> </detail> </soapenv:Fault> </soapenv:Body>
> > </soapenv:Envelope>
> >
> > Any inputs towards appropriately troubleshooting and resolving this
> > issue would be appreciated.
> >
> > Regards.
>
Re: WS-Security UsernameToken Issue (WSS4J-based Java client vs. .NET server)
Posted by Soactive Inc <so...@gmail.com>.
<soapenv:Fault> <faultcode>soapenv:FailedAuthen tication</faultcode>
<faultstring>The security token could not be authenticated or
authorized</faultstring> <faultactor>
http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx</faultactor>
<detail> <string/> </detail> </soapenv:Fault>
On 3/15/06, Barry McGann <ba...@thb.scot.nhs.uk> wrote:
>
> What error message are you getting?
>
>
>
> Soactive Inc wrote:
> > Hi All,
> >
> > I am trying to access a .NET service with a Java/Axis client (using
> > WSS4J) and am getting a security-related error. Here are the details:
> >
> > * Web Service: on .NET uses WS-Security UsernameToken (with Password
> > Digest)
> >
> > * Request Message
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
> > http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> > <soapenv:Header> <wsse:Security xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
> > <wsse:UsernameToken xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
> > <wsse:Username xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">TestDev</wsse:Username>
> > <wsse:Password Type="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest
> "
> > xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">R7bh5dDlYgjCurx6Dwq9ki39lQg=</wsse:Password>
> > <wsse:Nonce xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">/tA24bdIc0uwX7euUqvMVQ==</wsse:Nonce>
> > <wsu:Created xmlns:wsu="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> ">2006-03-14T22:34:50.971Z</wsu:Created>
> > </wsse:UsernameToken> </wsse:Security> </soapenv:Header>
> > <soapenv:Body> <ValidateEmail
> > xmlns="urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2">
> > <Email
> > xmlns="urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2">
> > testuser@myco.com <ma...@myco.com></Email> </ValidateEmail>
> > </soapenv:Body> </soapenv:Envelope>
> >
> >
> > * Response Message
> >
> > <soapenv:Envelope xmlns:soapenv="
> > http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
> > http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body>
> > <soapenv:Fault> <faultcode>soapenv:FailedAuthentication</faultcode>
> > <faultstring>The security token could not be authenticated or
> > authorized</faultstring> <faultactor>
> > http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx
> </faultactor>
> > <detail> <string/> </detail> </soapenv:Fault> </soapenv:Body>
> > </soapenv:Envelope>
> >
> > Any inputs towards appropriately troubleshooting and resolving this
> > issue would be appreciated.
> >
> > Regards.
>
Re: WS-Security UsernameToken Issue (WSS4J-based Java client vs. .NET server)
Posted by Soactive Inc <so...@gmail.com>.
<soapenv:Fault> <faultcode>soapenv:FailedAuthen tication</faultcode>
<faultstring>The security token could not be authenticated or
authorized</faultstring> <faultactor>
http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx</faultactor>
<detail> <string/> </detail> </soapenv:Fault>
On 3/15/06, Barry McGann <ba...@thb.scot.nhs.uk> wrote:
>
> What error message are you getting?
>
>
>
> Soactive Inc wrote:
> > Hi All,
> >
> > I am trying to access a .NET service with a Java/Axis client (using
> > WSS4J) and am getting a security-related error. Here are the details:
> >
> > * Web Service: on .NET uses WS-Security UsernameToken (with Password
> > Digest)
> >
> > * Request Message
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="
> > http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> > <soapenv:Header> <wsse:Security xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
> > <wsse:UsernameToken xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
> > <wsse:Username xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">TestDev</wsse:Username>
> > <wsse:Password Type="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest
> "
> > xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">R7bh5dDlYgjCurx6Dwq9ki39lQg=</wsse:Password>
> > <wsse:Nonce xmlns:wsse="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">/tA24bdIc0uwX7euUqvMVQ==</wsse:Nonce>
> > <wsu:Created xmlns:wsu="
> >
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
> ">2006-03-14T22:34:50.971Z</wsu:Created>
> > </wsse:UsernameToken> </wsse:Security> </soapenv:Header>
> > <soapenv:Body> <ValidateEmail
> > xmlns="urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2">
> > <Email
> > xmlns="urn:ws-mycoservices-com:mycoEmailValidation:EmailValidation:v2">
> > testuser@myco.com <ma...@myco.com></Email> </ValidateEmail>
> > </soapenv:Body> </soapenv:Envelope>
> >
> >
> > * Response Message
> >
> > <soapenv:Envelope xmlns:soapenv="
> > http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
> > http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body>
> > <soapenv:Fault> <faultcode>soapenv:FailedAuthentication</faultcode>
> > <faultstring>The security token could not be authenticated or
> > authorized</faultstring> <faultactor>
> > http://ws.mycoservices.com/mycoEmailValidation/V2/EmailValidation.asmx
> </faultactor>
> > <detail> <string/> </detail> </soapenv:Fault> </soapenv:Body>
> > </soapenv:Envelope>
> >
> > Any inputs towards appropriately troubleshooting and resolving this
> > issue would be appreciated.
> >
> > Regards.
>