cancel
Showing results for 
Search instead for 
Did you mean: 

Using SSO in a webservice

Former Member
0 Kudos

Is there any documentation available on how to properly set up a web service call to a BLS that has a JCO transaction requiring SSO? We approached it like any other web service call and set it up normally, but I wonder if there is anything special we have to do since in the JCO Transaction there are two parameters that have to be passed into it in order for the SSO to work. In JCO, the SAPUserName parameter must be "$MYSAPSSO2$" and the SAPSSO2Ticket must be "SAPSSO2Ticket". Is it possible that the webservice does not pass these parameters because we are getting an SSO error about the SSO not being authenticated?

Accepted Solutions (0)

Answers (1)

Answers (1)

jcgood25
Active Contributor
0 Kudos

Let me see if I understand this...

You have an MII TRX using JCO and SSO configured to exectue the BAPI as the logged in user. This works fine when running from the Workbench or even a runtime webpage/iCommand, etc.

You are now trying to call this same TRX as a webservice through WSDLGen/SOAPRunner and expecting the same SSO to go through to ECC? How is the webservice calling entity / user being authenticated into UME such that they will actually have the SSO2Ticket to send through to ECC?

Former Member
0 Kudos

This is what we are kinda asking you, but to answer your question, "You are now trying to call this same TRX as a webservice through WSDLGen/SOAPRunner and expecting the same SSO to go through to ECC?", yes we expect to use the webservice and still pass the SSO credentials to the ECC. We don't know if it's supposed to "just work" or if we have to set something up or pass in the ticket or what. We need to know the recommended/best practice for doing it.

jcgood25
Active Contributor
0 Kudos

The SSO2Ticket comes with the NW UME login session, so assumedly if you are authenticating in a manner that creates a valid user session it should be able to pass through the webservice trigger.

What have you found so far through testing?

Former Member
0 Kudos

What we have found is that we are unable to authenticate the SSO ticket using a web service. We ended up creating a work around using a BLS to read the SSO ticket. Then using an Xacute Query we can display the data to the webservice. IT works now, but we are not sure how the webservice is supposed to be setup with SSO.