SSO not working between SAP GUI for windows and WD ABAP

[Former Member]

Hi Experts,

We access our custom webdynpro application from SAP Inbox( tcode-SBWP) .We login to SAP GUI from windows with userid and password then once we click any item from SAP inbox then the respective WD ABAP application opens in a new IE browser .But it asks for netweaver userid and password to load WD Application in browser.

So can anyone help me how to avoid this logon screen or is there any possible to SSO for this case.We don't use SAP Portal . 

Is there any specific parametere we have to include in that WD ABAP application?

or do we need to any settings in SICF for this service?

[LutzR · Accepted solution]

Hi Avishek Das, I am not sure if I got your scenario correctly. But if you are looking to bridge the SSO-gap between Windows GUI and some ABAP based web application and both GUI application and web application are running on the same system and you are using custom code to call the web application from the GUI application - then check this note: "612670 - SSO for local BSP calls using SAP GUI HTML Control" http://service.sap.com/sap/support/notes/612670.

Even though it tells us about BSP it is valid for all types of ICF services.

This does only work with IE since it uses GUI's html control which is a part of IE Installation.

Have fun,

Lutz

[Former Member · Accepted solution]

Hi  Lutz,

Really it's helpful information and thanks a lot for that.

I have checked above note and as per the note if any WD ABAP or any kind ICF application is called from any other application(ex-bsp) then we can use this "Enable_SSO"  method from calling application or method .But for my case if you see the attached screen there you will find one entry in SAP Inbox (first entry as per red arrow)and once we click this link one custom wd abap opens in a new browser with logon screen and this is navigating not from ano other custom application.

So where I will  implement the "Enable_SSO"  method because navigation mechanism from SAP inbox is a standard process. As per custom logic we have just set one custom wd abap link to the SAP inbox task item.When we click task item from inbox then this custom wd abap triggers directly not from the other application .Not sure I am able to make understand you or not