Entra ID (Azure) instead of ISAM’s LDAP

[former_member820544]

Hi All,

We are using SAP BO 4.3 SP1 Patch13 (Linux OS) with LDAP authentication. Other than Dealers, all our users will login to Launchpad (with LDAP authentication) to access the reports. Dealer will access only 4 reports (OpenDocument links(ISAMs LDAP)) through our portal without connecting to our network and without logging into Launchpad. Now our client is planning to replace the LDAP authentication with Entra ID (Azure), as part of this, initially they are planning to be implementing this LDAP replacement with Entra ID for dealer’s login (who is accessing only 4 reports through OpenDocument links which are present in our portal with BOE junction ISAMs LDAP). To access those 4 reports, dealers should be part of one LDAP group in BO and we have configured SSO by updating the parameters in custom files at location:

<BOEInstallDir> /tomcat/webapps/BOE/WEB-INF/config/custom

File: FioriBI.properties

authentication.default=secLDAP

authentication.visible=true

cms.default= <our cms system name>

File: global.properties

trusted.auth.user.param=iv-user

sso.enabled=true

trusted.auth.user.retrieval=HTTP_HEADER

File: OpenDocument.properties

authentication.default=secLDAP

cms.default=<our cms system name>

Now the question is, is our current BO version (4.3 SP1 Patch13 on Linux OS) will support Entra ID? If yes,

1. How can we configure Entra ID(Azure) in place of ISAM’s LDAP.

2. Can we maintaining 2 configurations (LDAP for BO users and Entra ID(Azure) for dealers who are access 4 reports through OpenDocument links which are present in our portal).

Thanks in advance for your answers and help.

Note: User Groups which dealers belongs to will be maintained directly in Entra ID. There will not be an on prem LDAP or AD instance