Hello Experts,
we have some problems with configuring the UWL-function "Refresh completed items". I could localize the problem to the used WebFlowConnector-Destination.
If we use for authentication of the current user "LogOn Ticket", then the following Exception
Problem occured while jco connecting or trying to invoke jco methodSUWL_NOTIF_START_WORKITEMS_MONjava.lang.Exception: Problem occured while creating JCO client for destination: xxxx
is raised.
I found some Information, that JCo 3.0 could not work with SAP-LogonTickets. So my first question
1) Where can I found the version number in the NWA?
If we use for authentication of the current user "Assertion Ticket", then the following Exception
#2.0 #2015 03 25 11:12:01:138#+0100#Error#com.sap.engine.services.security.authentication.loginmodule.ticket#
#BC-JAS-SEC#security#C0000AB00014000B00000061000012CC#3347151000007680#sap.com/com.sap.netweaver.bc.uwl#com.sap.engine.services.security.authentication.loginmodule.ticket#Guest#0##87CAF98BCD6911E496A40000003312CF#87caf98bcd6911e496a40000003312cf#87caf98bcd6911e496a40000003312cf#0#Thread[UWL Pooled Thread:3,5,ApplicationThreadGroup]#Plain##
Error while creating assertion ticket on demand. No logged in user found.#
#2.0 #2015 03 25 11:12:01:138#+0100#Error#com.sap.security.core.server.destinations.lib.AssertionTicketRetriever$GetAssertionTicketPrivAction#
#BC-JAS-SEC#security.class#C0000AB00014000B00000062000012CC#3347151000007680#sap.com/com.sap.netweaver.bc.uwl#com.sap.security.core.server.destinations.lib.AssertionTicketRetriever$GetAssertionTicketPrivAction.run()#Guest#0##87CAF98BCD6911E496A40000003312CF#87caf98bcd6911e496a40000003312cf#87caf98bcd6911e496a40000003312cf#0#Thread[UWL Pooled Thread:3,5,ApplicationThreadGroup]#Plain##
An error occurred while trying to generate an SAP authentication assertion ticket.
[EXCEPTION]
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor611.invoke(Unknown Source)
...
is raised. In the called backendsystem we get a
CALL_FUNCTION_SIGNON_INCOMPL-DUMP
So the second question is:
2) Where can I look for further investigation?
I am out of ideas.
Some informations beside.
We use SAML2 for authentification. In the Portal System Landscape we configured for the Logon Method in the User Managment Section "SAPLOGONTICKET" with "Authentication Ticket Type = SAP Logon Ticket". If we here choose SAML2 for Logon Methode, the UWL-IView throws an other error:
The attribute "logonmethod" of the backend system with alias ""xxxx" (system landscape: "EnterprisePortal")" has the invalid value "SAML 2.0".
Cannot provide authentication data for user "xxxxxxxx" (unique ID: "USER.PRIVATE_DATASOURCE.un:xxxx") and the specified backend system.
Please adjust the value of the system attribute. Supported values are "SAPLOGONTICKET", "UIDPW" and "X509CERT".
SAP Service says, that UWL could not work with SAML2 so, you we configured it with SAPPLOGONTICKET.
3) Could this be relevant?
Thanks for replies and Greetings
Thomas