cancel
Showing results for 
Search instead for 
Did you mean: 

IBM SSO LDAP Users Login Issue in 4.3 SP04 patch2

Shiva2
Newcomer
0 Kudos

Dear experts,

We have the problem with SSO to http://<boserver>/BOE/BI via third party LDAP users ( LDAP Server Type: IBM Directory Server) login through internal portal page with LDAP user in 4.3 Versions ( 4.3 SP03, 4.3 SP04 Patch 2) and working as expected in current version of SAP BO ( 4.2 SP08 Patch09).

Workflow: In internal Portal , their will be one google chorme icon , LDAP users will login into internal portal page and clicks the chrome icon then one more new window will open in chrome with directly landed SAP BO Home page.

Above workflow scenario working as expected in 4.2 SP08 Patch09 with no issues from past few years , Current version of SAP BO 4.2 versions is Out of Support this year ( 31 Dec 2024) and we are going to parallel upgrade with new windows server 2019 with fresh installations of 4.3 SP04 Patch02.

In 4.3 SP04 patch2 version, LDAP Users able to login into our internal portal page and click the chorme icon then one new window in chorme will open as expected but instead of SAP BO application home page , we are getting SAP BO login page.

Please find the below screenshot for reference and also same configuration we have done in 4.2 and 4.3 versions , refer below.

Please let me know , any configuration i have missed in 4.3 or any other configuration i have to do in 4.3 version for solving the issue.

Shiva2_1-1711198420352.png

Implemented steps in SAP BO 4.2 SP08 Patch09 and 4.3 SP04 Patch2.

Step-1 : Done the LDAP setup in SAP BO CMC.

Step-2: SSO Configuration

Shiva2_2-1711198912319.png

Step-3: Creating a Global. Properties file, placed in below locations.

For Windows:<INSTALLDIR>\SAP Business Objects Enterprise XI4.0\warfiles\webapps\BOE\WEB-INF \config\custom\

For Tomcat installed on Windows:<INSTALLDIR> \Tomcat\webapps\BOE\WEB-INF\config\custom

Shiva2_3-1711199018311.png

Step-4:BILaunchpad.properties/Fiori.properties:

authentication.visible=true

authentication.default=secLDAP

Step-5: Re-builded the Tomcat cache.

Note: Issue persists in standalone and cluster environment and LDAP users able to login with direct application URL.

Appreciate if some one can help me on this ASAP.

Thanks & Regards,

Shiva

 

Accepted Solutions (0)

Answers (0)