Skip to Content
avatar image
Former Member

BSP Context and SSO2

Hi,

I'm launching my BSP applicatios through a login page, copy of systemsession_single_frame.htm, so when the BSP is unloaded a logoff event

is raised.

My problem cames when a launch another BSP application. Sometimes it loose the

context after the first event. I think that it is because sometimes the logoff page is threatened

after the new BSP query.

What can i do to solve this?

Thans in advance

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Nov 19, 2003 at 02:54 PM

    Hallo Angel, (I am not sure how many of these segments are names versus surnames:)

    You question is still slightly confusing. Mostly due to English use. So let me ask you some questions back, and then we take it from there.

    You seem to have two BSP applications, say A1 & A2. Yes?

    Now if you run A1, everything should work fine. The session protect frame will close the session when it is done.

    Now we come to the problem: What do you mean with "launch another BSP application"? Is this second BSP application run in the same window (inside frame)? Or will it run separately inside another browser window?

    And the other part of the question that is confusion: "logoff page is threatened". In English threatened would mean that somebody puts a gun in your face and asks very nicely for money. But this is not what you mean. Maybe you can describe this some more. (Or use Spanish, and we will try to have to have it translated.)

    What I suspect, but I am not sure, it that you have two applications running in two windows. When the first close, it deletes SSO2 cookie, which was also used for the second session. And then it can not continue to work, without requiring authetication information again. (If yes, we have solved this problem recently.)

    Also, you can look at BSP application ITSM for an example.

    bye, brian

    Add comment
    10|10000 characters needed characters exceeded

    • Yes, you found the answer before I could give it again.

      So let me give you the explaination. The problem is that when you do a top.href = newurl, we are actually starting *TWO* requests to the server. The one is the loading of the new_url. The other is from the popup window which is still trying to close the previous session. And where we get a race condition. The new app is started, and then the closing sequence comes and deletes all of its session cookies. The small delay helps to give the popup window time to first close the previous session.

      bye, b.