Problem with BSP Iview.

[Former Member]

Hi ,

i have created an BSP Iview in EP . While accessing my BSP Iview for the first time it's promting for Userid and Pwd and it's fine.

But, My BSP Iview is not prompting for Userid and Pwd , if i access it for the second time .

Even after the log off and login of my EP ,still BSP Ivw was not propmting for userid and pwd.

I have set Stateless for my BSP Application ,and

In Iview properties i have turned off the Client side cache .But of no use .

Regards ,

J

[Former Member · Accepted solution]

HI,

This happens because the NetWeaver portal generates a Browser cookie "MYSAPSSO2",which contains the information such as userid,timestamp,session id,name of server from which request came (in case of BSP iview,information of WAS on which BSP application hosted).

So,after authentication for the first time,the information is there in the cookie,in the browser.Thus,even if you logoff the Portal and login again,but in the same browser window,the cookie would be there and so it wouldn't prompt for the login id etc. for the same server again.But if you open the portal in another window,it would prompt for userid/password.

Regards,

Siddhartha Jain

[Former Member · Accepted solution]

Thanks Siddartha to explain this..

Is there any workaround to handle this ?

[Former Member · Accepted solution]

Hi Siddardha ,

Then it would be a problem na . If a same system is used by other persons ( Evn they give their Portal id ,they will get my results. )

Wht's the soln ?

Rgds,

J

[Former Member · Accepted solution]

HI,

If the same system is used by another person,he wouldn't get the same results,as the session is handled by the Portal and on logoff it is terminated by the DSM terminator.

But do ensure to check the "supports Portal Integration " checkbox of the BSP application ,to ensure registration of stateful BSP applications so that the portal can inform the BSP application when it is closed .

For stateless BSP applications,the session is automatically refreshed for each request.

You can get more details from the link

<a href="http://help.sap.com/saphelp_470/helpdata/en/83/132197c3564643af326a5ebccb604f/content.htm ">http://help.sap.com/saphelp_470/helpdata/en/83/132197c3564643af326a5ebccb604f/content.htm</a>

The only consequence of using the same browser window to log onto the portal as different user is that the user is not prompted for credentials for the WAS on which your BSP application is hosted.

Do you want the user to validate his credentials for the WAS on which BSP application is hosted,even after he has been authenticated on the Portal?

I suppose,one of the purposes of the Portal is to provide single point of access to multiple resources without user having to validate credentials again and again.

Still,if you want to do that,you can use javascript's window.close() to explicitly close the browser window after user logs out,but for that you would have to edit the Portal logoff page.

Regards,

Siddhartha

[Former Member · Accepted solution]

Hi Siddarth,

Thank you.

Where i hav to set the javascript .? in which evnt handler of the BSP Page ?

And My R/3 is connected with LDAP,so that,i am able to access my MSS/ESS Applications without specifiying Userid and Pwd.

But why My BSP is asking for Pwd ? How to Acieve SSO for my BSP Applications in the Portal ?

Regards,

J

[Former Member · Accepted solution]

HI,

The problem can be solved by enabling SSO from your Portal to the WAS and there wouldn't be any need for javascript.Morover,the javascript needs to be called on logoff from Portal,not from BSP pages,so you would have to modify standard Portal page for that.

For SSO,you can refer to the thread and the links mentioned in it.

<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=74657&messageID=803970">https://www.sdn.sap.com/irj/sdn/thread?threadID=74657&messageID=803970</a>

Regards,

Siddhartha