cancel
Showing results for 
Search instead for 
Did you mean: 

Single Sign On Error with Portal bookmarks.

Former Member
0 Kudos

Hi,

We have the below scenario with one of our portals. Our configuration is below.

EP6 SP21

WAS 6.40

SSO configured(SPNEGO with Kerberos Authentication)

Scenario:

From our portal, we have links to SAP Back end system(R/3, BW,etc). Since SSO is configured, whenever a user clicks a back end system from the Portal, he will be automatically logged into that system without having to enter user name and password.

However, a user wants to be able to click on a bookmarked URL to a web report in the SAP BW back end without going through the Portal.

Method used by user

· Open an internet browser and go to Google.com web page

· Open a 2nd internet browser and go to our Portal Web page

· Check task bar and noticed only one IEXPLORER.EXE is on

· Go to the browser with Google.com displayed and go to favourites and select BW Bookmark

· Managed to log in to the BW Webreport via Single Sign-On, no need to use Username and Password

· But when we go to an email with URL(bookmark URL for BW webreport) and select URL, a new session opens, an error occurs and the user cannot log in to the BW web report via SSO. They are prompted with the login screen to insert username/password.

I did a quick check and realised that this scenario only occurs when there are multiple IEXPLORER.EXE sessions in the Task Manager.

Please advise on how we can resolve this SSO error.

Thanks in Advance

Accepted Solutions (0)

Answers (1)

Answers (1)

detlev_beutner
Active Contributor
0 Kudos

Hi Dinakar,

This is "by design". If there is only one instance of IE running and you have logged into the portal in one IE window, you receive the SSO2 cookie which then is passed to the backend when calling the report (in the same or in antoher window of the same IE instance). If you open the backend link in a new IE instance, there is no SSO2 cookie to be passed on to the backend.

A workaround would be not to use the backend URL directly but a component within the portal which redirects to the backend (the AppIntegrator iView itself and the URL to it would do the trick, for example).

Hope it helps

Detlev