Skip to Content
avatar image
Former Member

Lumira will log off a serialized session that has been passed to opendoc


We have a custom portal which uses opendoc to view a story or explore a data mart. The user's BOE session is passed to opendoc either as a serialized session or as a logon token.

Serialized session is ideal, because it doesn't create another user session (which will consume a license seat). However, Lumira is logging off the serialized session when the opendoc tab is closed, which will also log the user out of the custom portal.

Ideal Solution: Lumira shouldn't log off a serialized session. The session was not established by Lumira and therefore should not be closed by Lumira.

Workaround: Use logon tokens for opendoc. This will consume concurrent license seats. Load opendoc in an iframe, try to override the session closing function (?)

Is there any other workaround?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 27, 2017 at 09:27 PM

    This behaviour is actually by-design and documented in the what's new guide for BI: This behaviour was something that was much asked for by our customers.

    You could try to move towards using a logon token instead which should allow you to set number of logons and I believe also a time out limit. As for your questions about logging on, getDefaultToken has its own lifespan and when re-used it will create addistional logon using up licenses. createLogonToken allows you to set a life span and max usage for the token.

    - Ludek Senior Support Engineer AGS Product Support, Global Support Center Canada
    SAP is now offering chat support. For more details please see KBA 2213344 - How to start a chat with SAP Support[video]
    Follow me on Twitter:

    Add comment
    10|10000 characters needed characters exceeded