Crystal session management via open document

[Former Member]

We are using open document to execute a report from an enterprise portal. When we use open document the first time everything is fine. However, if we log out of the portal, login in as a different user, and execute the same report the first user's session is used in Crystal. How could this server-side session be cleaned up so that each time open document is used the logon token being sent is used and a new server side session is established?

Thanks.

Edited by: Richard Mills on Sep 10, 2008 9:58 PM

[Former Member · Accepted solution]

Hello Richard,

-Whenever we create any token, we must use valid method to pass user credentials to the system.

-If you are using createLogonToken() or createWCAToken(), then these methods take validminutes as a parameter for which user session will be valid.After those number of minutes will be finished, user sesion will be expired.

-However if you are using getDefaultToken(), then only way to clear user Session is to call enterpriseSession.logoff() which will close session for that user.

-For more information on this method, please go to the following URL :

http://devlibrary.businessobjects.com/BusinessObjectsXIR2SP2/en/devsuite.htm---->BusinessObjectsEnterpriseSDK->JavaAPIReferance--->Interface ILogonTokenMgr

Thanks,

Chinmay

[Former Member]

We created an intermediate page between the portal and openDocument.jsp to invalidate the session then forward on the request to solve the problem.

[Former Member]

Are you using the java or the dotnet opendocument implementations?

What is the exact version of your Business Objects Enterprise product including the level of patches you have applied on it?

Cheers