cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SBOP BI Platform 4.3 SP04 Patch 10: Logon failed for RESTful WebServices

mwahrhusen88
Explorer
3,107

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?

mwahrhusen88_0-1738311474284.png

Thanks
Matthias

Accepted Solutions (1)

Accepted Solutions (1)

SOFIMA
Explorer
0 Kudos

Same here... after updating BO 4.3  SP3 Path 5 to 4.3 SP04 P10

After 4 hours to update ... need to restore backup...

mwahrhusen88
Explorer
0 Kudos

Hope the solution works for you. 

Answers (2)

Answers (2)

mwahrhusen88
Explorer

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

SOFIMA
Explorer
0 Kudos
ok, i just do that on actual version. Now need to find when i can update to SP3 P10, thanks
mwahrhusen88
Explorer
0 Kudos
We did it after the update - not sure if your approach will work.
Scw3
Discoverer
0 Kudos

Thanks for adding this really helpful, also having the same issue after updating BO 4.3 SP04 Patch10. Could I ask, where do I add the parameter "-Djdk.tls.client.protocols=TLSv1.2" in tomcat?  Not the biggest Tomcat user to be honest.  Thanks for your time

mwahrhusen88
Explorer
0 Kudos
You have to use the tomcat config tool. On Windows you can find it in your start menu.
Scw3
Discoverer
0 Kudos
Great, thank you so much 👍
SOFIMA
Explorer
0 Kudos
Hi, ok after update, same problem.. but your solution working !! thanks very much !
ayman_salem
Active Contributor
0 Kudos

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

mwahrhusen88
Explorer
0 Kudos
Thanks Ayman, but we already checked all these steps. Furthermore we did not change any configuration.
ayman_salem
Active Contributor
0 Kudos

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.

ShawnH
Newcomer
0 Kudos
Any updates on this? I also saw this error after upgrading to patch 10, but I was on SP04 patch 6 prior to upgrading. This only occurred on the https address I was using (with port 8443). If I enabled the http address (which used port 8080) the BI platform would successfully login. Prior to the upgrade, I hadn't changed the RESTful service URL, and changing it now did nothing. I don't have a load balancer. I don't believe I'm dealing with a self-signed certificate here. Any tips on where to set the TLS version at? When I opened the tomcat configuration app (the one that installs with the Crystal Server install), I didn't see a place to set this. I also had to clear and rebuild the tomcat work directory to get the site working after the upgrade (CMC started working after this was done, no effect on the BI though).
mwahrhusen88
Explorer
0 Kudos

No update so far - I will open a support case and keep you updated.