Symptom
Executing a service from the Web Service Navigator results in the following error on the Web Service Navigator screen.
Web service returned error. Fault Code: "(http://schemas.xmlsoap.org/soap/envelope/)Server" Fault String: "Client protocol has thrown an exception. Protocol name is [SecurityProtocol]. See nested exception for details. Method Info: Component:<Custom_Component> method : <serviceInterface>(requestId)= (null)""
Below errors are seen in the TSHW traces :
Client protocol has thrown an exception. Protocol name is [SecurityProtocol]. See nested exception for details.
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [SecurityProtocol]. See nested exception for details.
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.invokeHandlerRequest(SOAPTransportBinding.java:1163)
...........
...........
Caused by: com.sap.engine.interfaces.webservices.runtime.ProtocolExceptionExt: No logged in user found.
at com.sap.engine.services.wssec.srt.protocols.ConsumerSecurityProtocol.handleRequest(ConsumerSecurityProtocol.java:177)
...........
...........
Caused by: java.lang.IllegalStateException: No logged in user found.
at com.sap.security.core.server.jaas.SAPLogonTicketHelper.createAssertionTicket(SAPLogonTicketHelper.java:496)
Read more...
Environment
- SAP NetWeaver 7.3
- SAP enhancement package 1 for SAP NetWeaver 7.3
- SAP NetWeaver 7.4
- SAP NetWeaver 7.5
Product
Keywords
java, webdynpro, security, Error while creating assertion ticket on demand, No logged in user found, Assertion ticket could not be retrieved, Client protocol has thrown an exception, com.sap.security.core.server.jaas.SAPLogonTicketHelper.createAssertionTicket, Web service returned error, com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException , KBA , BC-JAS-SEC , Security, User Management , BC-ESI-WS-JAV-RT , Runtime , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.