Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Token not being assigned to Open Document Link

After upgrading to BI 4.1 SP5 we have notice that a bttoken is no longer being assigned to our OpenDocument link.  This is causing our users to be presented with a user id/password log in screen instead of the detail level report.

Prior to clicking on the OpenDocument link are users are logging into a .net application which then uses the Restful service to create a log in token.  We have confirmed the log in token is being generated as expect and our users are able to access the summary reports that the token is being assigned to.  Within the summary report is where we provide an additional OpenDocument link, which will take you to a detail level report. This is where we are no longer able to access the token. 

We have notice that this issue is temporary fixed after performing a restart of Tomcat, however after reaching either the token time out setting or by killing the first login session the links are no longer working.  Prior to upgrading "BI4.1 SP2" we were running into similar issues until we implemented the below lines into a custom OpenDocument.properties file.  This fixed our issues at the time, but now is no longer working in the new SP5 version.

logon.allowInsecureEmbedding=true

sso.types.and.order=sapLogonToken

We are currently working with SAP regarding this issue, but any additional assistance would be greatly appreciated.

Thanks Paul

replied

SAP was able to confirm this issue was present when upgrading the system from BI 4.1 SP2 to BI 4.1 SP5.  We have since role back to SP2 and then upgraded to SP6.  We are no longer seeing this issue in SP6.

Thanks Paul

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question