2025 Jan 31 8:18 AM - edited 2025 Jan 31 8:18 AM
Hi guys,
after updating from 4.3 SP02 P8 to 4.3 SP04 P10 we are facing logon issues on the BI Launchpad:
We have a second server which was not updated yet. I compared all config files - no differences.
In the Webapp_BIlaunchpad_trace files I see he following error:
No logon token provided in the X-SAP-LogonToken HTTP header or query parameter. (RWS 00008)
I'm running out of ideas. Anybody facing the same issue?
Thanks
Matthias
Request clarification before answering.
Same here... after updating BO 4.3 SP3 Path 5 to 4.3 SP04 P10
After 4 hours to update ... need to restore backup...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We got help from SAP Support:
Copy the Tomcat (or load balancer) https URL into the browser address bar:
Note: it must be the same URL the users use to access the system
Press enter to navigate to this URL
Click , next to the URL
A window should open with the certificate details (Certificate Viewer)
Select the 'Details' tab
Click 'Export'
Save the certificate, but change the format to DER Encoded Binary (.der)
Click Save
Copy the exported certificate to the machine(s) where Tomcat is located
Then follow the steps below 'Installing the Certificate
Open a command prompt
Navigate to the following location: cd C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin
Run
keytool -import -noprompt -trustcacerts -alias <uniquealias> -file <path to .der file> -keystore ../jre/lib/security/cacerts -storepass changeit
e.g. keytool -import -noprompt -trustcacerts -alias CTSPM -file c:/ssl/tomcatcert.der -keystore ../jre/lib/security/cacerts -storepass changeit
Also Add the below parameter in tomcat configuration.
-Djdk.tls.client.protocols=TLSv1.2
Restart Tomcat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are many reasons for it
It could be the wrong configuration of the RESTful Access URL,
1 Check the access URL of the RESTful service under CMC-> Applications-> RESTful Web Services
2. If you use Load Balancer, check that you use the correct RESTful URL
3. Be aware that a self -signed certificate is no longer supported
4. TLS 1.3 is currently not supported and TLS 1.2 should be set to be used exclusively in Tomcat configuration
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Many change between SP02 and SP04, so that many existing/new configurations should be adapted. For example, you can use the relative URL path for a RESTful URL
TLS 1.2 should be set exclusively in the Tomcat configuration (Tomcat use TLS 1.3 by default)
Another tip: After the upgrade, do not forget to remove the content of the Tomcat work directory.
| User | Count |
|---|---|
| 17 | |
| 8 | |
| 8 | |
| 6 | |
| 4 | |
| 4 | |
| 4 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.