[Solved] Unable to load groups on Fiori Launchpad with error "Invalid URI segment 'PageSets(''"

"Failure - Unable to load groups" and in the HTTP trace you get error "400 Bad Request"
While accessing Fiori Launchpad from Apache Reverse Proxy, you get the error in browser Unable to load groups, and your application will not open. You can see below-mentioned request getting failed.
Request:
/sap/opu/odata/UI2/PAGE_BUILDER_PERS/PageSets('%2FUI2%2FFiori2LaunchpadHome')?$expand=Pages/PageChipInstances/Chip/ChipBags/ChipProperties,Pages/PageChipInstances/RemoteCatalog,Pages/PageChipInstances/ChipInstanceBags/ChipInstanceProperties,AssignedPages,DefaultPage
In the response of the request, you can see the message: Invalid URI segment 'PageSets(''
However, if you use intranet (without any Reverse Proxy), the Fiori Launchpad can be loaded properly.
Root cause:
When we use Apache proxy, the reverses proxy automatically decodes the entire URL before forwarding the request to the backend. '%2F' is decoded to '/'.
Solution:
Configure proxy server to make sure it will pass the request URL not decoded. check the below configuration using AllowEncodedSlashes NoDecode and nocanon
Apache virtual host config:
ServerName sap.mysite-it.in
ServerAlias www.sap.mysite-it.in
ServerAdmin shirish.bathe1@mysite-it.in


ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

#Disable proxy check, as we don't have the valid certificate for backend server and it only can access through HTTPS
SSLEngine on
SSLProxyEngine on
SSLProxyEngine on
SSLProxyVerify none 
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off

SSLCertificateFile /ssl/wildcard_ssl/my.crt
SSLCertificateKeyFile /ssl/wildcard_ssl/my.key
SSLProxyCACertificatePath /etc/ssl/certs
#SSLProxyMachineCertificateFile /ssl/wildcard_ssl/combined.pem

ProxyPreserveHost on
AllowEncodedSlashes NoDecode

ProxyPass /     https://IP:port/ nocanon
ProxyPassReverse /  https://IP:port/

Comments

Post a Comment

Popular posts from this blog

Git Auto Increment tag

If you want GIT tag autoIncrement with one version number after each build you can use below shell script(./gittag.sh) as the hook. Scrip will find last committed TAG which starts with  ENV_TAG_PREFIX ( QA_V) and creates next release TAG then push tag to GIT. VERSION_MODE   [major|minor|revision|buildNumber - These are the possible value. each time one version is a tag with GIT. By default, buildNumber is pass which increment last digit in release tag like(x.x.x.1 to x.x.x.2). So if you want major release then you can pass major as option which tag GIT with major release  like (1.x.x.x to 2.x.x.x)] e.g. ./gittag.sh major       ./gittag.sh minor #!/bin/bash VERSION_MODE = $1 ENV_TAG_PREFIX = QA_V # "major": 1, # "minor": 0, # "revision": 0, # "buildNumber": 1 if [ "$VERSION_MODE" = "" ] ; then VERSION_MODE = "buildNumber" fi cd /path/to/your/git/checkout ...
Read more

Log rotate (catalina.out) of Tomcat

Rotate Catalina.out of tomcat on On Linux (Centos 7) server By default, Catalina.out file will not be rotated. To rotate it I have used logrotate. First, understand the  logrotate utility   Create tomcat file under /etc/logrotate.d/  using below command                               sudo vi /etc/logrotate.d/tomcat Press i to enable insert mode, past below script into file                                                                /opt/app/tomcat/logs/catalina.out {  su myuser myusergroup  missingok  notifempty  copytruncate  daily  size 5M  rotate 7 } Here /opt/app/tomcat/logs/catalina.out is path to your log file. press Esc key, then : wq!  to write and quite ...
Read more

Bypass SSL certificate check for Apache Axis2 client

For some reason, I wanted to totally ignore the certificate and trust store check with my Axis2 client stub implementations and I was looking for the solution. I came across a lot of articles which states about using  HttpsURLConnection to disable SSL check, but the problem is underlying Axis2 client doesn’t use the  HttpsURLConnection  Solution: We can use that TrustManager to create an SSLContext which trust all the servers. SSLContext sslCtx = SSLContext . getInstance ( "TLS" ); sslCtx . init ( null , new TrustManager [] { new TrustAllTrustManager ()}, null ); APIStub client = new APIStub ( url ); client . _getServiceClient (). getOptions (). setProperty ( HTTPConstants . CUSTOM_PROTOCOL_HANDLER , new Protocol ( "https" , (ProtocolSocketFactory) new SSLProtocolSocketFactory ( sslCtx ), 443 ));
Read more