Forum Discussion

SOAPUINewbie123's avatar
13 years ago

SOAP UI & Siebel: Cannot reauthenticate

Here is what I did:
1) Exported a WebService from Siebel.
2) Created a 'project' in SOAP UI.
3) Edited the line at the top (I think it might be called the 'end point'), by adding this &WSSOAP=1 at the end of the line giving:

http://server.domain.com/eai_anon_enu/s ... e&WSSOAP=1

4) Then I added the following lines in the SOAP Header:
<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"></wsse:Security>

<UsernameToken xmlns="http://siebel.com/webservices">MYUSERNAME</UsernameToken>
<PasswordText xmlns="http://siebel.com/webservices">MYPASSWORD</PasswordText>
<SessionType xmlns="http://siebel.com/webservices">None</SessionType>

5) Then running the request it gives the following error:
<siebelf:error>
<siebelf:errorcode>SBL-EAI-04501</siebelf:errorcode>
<siebelf:errorsymbol>IDS_EAI_WS_SECURITY_URLAUTH</siebelf:errorsymbol>
<siebelf:errormsg>Cannot reauthenticate operation E3MSalesMethodLOVQueryQueryByExample.(SBL-EAI-04501)</siebelf:errormsg>
</siebelf:error>

6) As an alternative, I can make the following setting change, in Request Properties.
Skip SOAP Action - set this to TRUE.
Then it gives:
<siebelf:errorcode>SBL-EAI-04313</siebelf:errorcode>
<siebelf:errorsymbol>IDS_EAI_WS_OP_NOT_FOUND</siebelf:errorsymbol>
<siebelf:errormsg>There is no active Web Service with operation named 'http://siebel.com/CustomUI:CustomMethodName'.(SBL-EAI-04313)</siebelf:errormsg>

Does anyone have some ideas on how to fix either error?
I tried other modes instead of none like Stateless etc.
I tried (in development) changing the WebService to authentication None and then exporting it and running it against the one with None set but it didn't seem to make a difference...
Any other ideas?

1 Reply

  • nmrao's avatar
    nmrao
    Icon for Champion Level 1 rankChampion Level 1
    1. You may also set the authentication details in Test Request properties.
    2. Also check if it requires any Domain / WSS-Password Type details from your service provider
    3. Do not need to remove soap action
    4. Check if the service is running with the provider.