| Author |
Message
|
| girish_kulkarni |
 Posted: Thu Nov 10, 2011 6:28 am Post subject: Actor or Role is not working for SOAPInput node |
 |
|
Apprentice
Joined: 08 Oct 2010
Posts: 32
|
Dear All,
I am using MB version 7.0.0.3 and toolkit version 7.0.0.0 as development environment. I have used ADAM as authentication and authorization.
I have enabled ws security using security profile and added my own actor(SOAP 1.1) or role(SOAP 1.2) name in my SOAPInput node (Advance property). But when I hit the web service with the role which i provided in SOAPInput node as
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:con="http://cds.gdt.com/ContraventionDetailsService/">
<soapenv:Header>
<wsse:Security soapenv:actor="124" mustUnderstand="1"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="unt_907818524">portalvrr</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ngi</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
<wsse:Security soapenv:actor="xyz" mustUnderstand="1"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="unt_907818524">portalvrr</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ngi</wsse:Password>
</wsse:UsernameToken>
</wsse:Security></soapenv:Header>
<soapenv:Body>
</soapenv:Body>
</soapenv:Envelope>
where SOAPInput node role property is set to "124"
message broker is giving exception
<faultstring>CWWSS5525E: The server cannot find the security header for a Web service with no actor.</faultstring>
But when i run with one actor as blank as below
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:con="http://cds.gdt.com/ContraventionDetailsService/">
<soapenv:Header>
<wsse:Security soapenv:actor="" mustUnderstand="1"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="unt_907818524">portalvrr</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ngi</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
<wsse:Security soapenv:actor="xyz" mustUnderstand="1"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="unt_907818524">portalvrr</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ngi</wsse:Password>
</wsse:UsernameToken>
</wsse:Security></soapenv:Header>
<soapenv:Body>
</soapenv:Body>
</soapenv:Envelope>
It is working fine. But it should work for role name which we give in SOAPInput node.
Please help me on this as i am not finding much in internet.
Thanks,
Girish Kulkarni |
|
| Back to top |
|
 |
| mgk |
| Posted: Thu Nov 10, 2011 6:45 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hello. I believe this was fixed recently, so you need to raise a PMR to get the fix.
Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| bielesibub |
| Posted: Fri Nov 18, 2011 3:24 am Post subject: |
|
|
Apprentice
Joined: 02 Jul 2008
Posts: 40
Location: Hampshire, UK
|
Girish,
This has been fixed, I've been using the fix for sometime now.
I notice that you are using mulitple ws-security headers in your requests, be aware that if you are going to be expecting requests from .Net clients, using WCF they will not be able to support this configuration!
Bielesibub |
|
| Back to top |
|
|
| girish_kulkarni |
| Posted: Fri Nov 18, 2011 3:48 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2010
Posts: 32
|
Hi bielesibub,
Thanks for ur information.
Could you please tell me the fix pack number and is it available in internet. We raised a PMR with IBM support centre, But till now,did not get any response from them.
Anyways, we are using java client for accessing our MB services. We are using SOAPUI for unit testing. |
|
| Back to top |
|
|
| bielesibub |
| Posted: Fri Nov 18, 2011 4:06 am Post subject: |
|
|
Apprentice
Joined: 02 Jul 2008
Posts: 40
Location: Hampshire, UK
|
Girish,
I don't have a fix pack number, here is the apar info;
Test fix for APAR IC76975:
WMB V7 - UNABLE TO RETAIN WS-SECURITY HEADERS WITH NON-BROKER ACTORS |
|
| Back to top |
|
|
| girish_kulkarni |
| Posted: Fri Apr 06, 2012 4:55 am Post subject: |
|
|
Apprentice
Joined: 08 Oct 2010
Posts: 32
|
| I got a fix pack from IBm which solved my issue |
|
| Back to top |
|
|
|
|
