| Author |
Message
|
| kumar.MBMQ |
 Posted: Mon Jun 08, 2015 6:49 am Post subject: no caller identity candidate that can be used to login. |
 |
|
Voyager
Joined: 06 May 2011
Posts: 93
|
I tried to hit the url through soap ui but error is thrown :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>security.wssecurity.WSSContextImpl.s02: com.ibm.websphere.security.WSSecurityException: Exception org.apache.axis2.AxisFault: CWWSS6500E: There is no caller identity candidate that can be used to login. ocurred while running action: com.ibm.ws.wssecurity.handler.WSSecurityConsumerHandler$1@6080a414</faultstring>
<detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope> |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Jun 08, 2015 6:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| That sounds like WS-Security isn't configured properly or the incoming message isn't set up properly. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 08, 2015 7:47 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| That sounds like WS-Security isn't configured properly or the incoming message isn't set up properly. |
I'd say the latter. The broker should (but not always) see a missing identity candidate before it tries to use the missing candidate in any authentication or authorization activity.
I'd say the OP hasn't made the necessary changes to SoapUI to add the WS-Security header and it's contents.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kumar.MBMQ |
| Posted: Mon Jun 08, 2015 8:29 am Post subject: |
|
|
Voyager
Joined: 06 May 2011
Posts: 93
|
| Vitor wrote: |
| mqjeff wrote: |
| That sounds like WS-Security isn't configured properly or the incoming message isn't set up properly. |
I'd say the latter. The broker should (but not always) see a missing identity candidate before it tries to use the missing candidate in any authentication or authorization activity.
I'd say the OP hasn't made the necessary changes to SoapUI to add the WS-Security header and it's contents. |
Thanks,
In the soap ui , in the request message I set the value ADD USERNAME TOKEN . I gave the credentials . it's working . |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jun 08, 2015 8:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kumar.MBMQ wrote: |
| Vitor wrote: |
| mqjeff wrote: |
| That sounds like WS-Security isn't configured properly or the incoming message isn't set up properly. |
I'd say the latter. The broker should (but not always) see a missing identity candidate before it tries to use the missing candidate in any authentication or authorization activity.
I'd say the OP hasn't made the necessary changes to SoapUI to add the WS-Security header and it's contents. |
Thanks,
In the soap ui , in the request message I set the value ADD USERNAME TOKEN . I gave the credentials . it's working . |
Now wouldn't it have been easier to just do that rather than posting here? There's a whole section of the SoapUI documentation on adding various kinds of credentials, which you clearly seem to know about as you've now added them.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
