Skip to Content

Rfc Library: SSO via SNC and RfcGetTicket


i am connecting to a WAS 6.20 system through SNC/Active Directory SSO, e.g. using

"SNC_MODE=1 SNC_PARTNERNAME=p:SAPServiceXXX@domain SNC_LIB=c:\windows\system32\gsskrb5.dll"

instead of "USER= PASSWD=" the RfcOpenEx logon string. This works fine, I can log on to the system and execute RFCs without having to provide the username and pw.

However, since I want the solution also to work with BSP, I need a SAPSSO2 ticket. No problem, RfcGetTicket() should get me one, says the documentation. But here's my problem:

I have to add not only "GETSSO2=1" to the connect string, but also the SAP username of the user, otherwise RfcGetTicket() returns only a "0" instead of the ticket (providing the password is not necessary).

Can someone confirm whether

a.) this behaviour is by design

b.) this should work, and when it does not, my server is not configured correctly


c.) there is some other way to get the ticket without having to provide the SAP username

On a side note, the documentation could mention that it is necessary to actually call a function module to get the ticket; calling RfcGetTicket() right after RfcOpenEx() does not work.



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Sep 26, 2005 at 10:45 AM

    Just in case anyone is interested in the "solution":

    I found out the empty SSO Ticket is only returned if if the (dummy) function module "RFC_PING" is called. If any(?) other module is used instead, the ticket gets returned as expected (even if RFC_PING is copied to e.g. "ZRFC_PING").

    This is a rather strange effect, I suspect this has something to do with internal optimizations.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.