How to enable AD authentication in 360Suite

How to enable AD authentication in 360Suite

Context

You want 360Suite to use AD authentication the same way BusinessObjects does it.

Procedure

As part of the AD authentication configuration on the Business Objects server, two files will have been created and saved on “C:\Windows\” directory (default).

  1. bscLogin.conf
  2. krb5.ini
  1. Copy these two files from the Business Objects server and paste them on the 360Suite Web Platform server the same directory, in the same directory, i.e. C:\Windows\.
  2. Open the 360Suite Web Platform Tomcat options, navigate to the Java tab and add the following lines to the Tomcat Java Options:
-Djava.security.auth.login.config=C:\Windows\bscLogin.conf
-Djava.security.krb5.conf=C:\Windows\krb5.ini



3. Navigate to the Log On tab and enter the AD Service Account Tomcat will use:

4. Click OK.
5. Restart the 360Suite Web Platform Tomcat for changes to take effect.

    • Related Articles

    • VSJ Authentication Was Not Performed For This Request

      Symptom When accessing 360Suite with its default login URL, the following error message appears: "VSJ Authentication Was Not Performed For This Request" Cause This typically happens when Active Directory (AD) SSO was enabled for 360Suite and the ...

    • How to configure 360Suite's Tomcat with HTTPS

      ? Purpose This article provides high‑level guidance for enabling HTTPS/SSL on Apache Tomcat 10.1.x. Because Tomcat is a third‑party application server, SSL configuration is outside the scope of our product support. The content below summarizes and ...

    • SAML Logon is showing the error "Problem Validating the Authentication Request"

      Symptom When logging to the application with the SAML Logon, the page loads and ends on this view : Cause The authentication request sent by the Identity Provider is not signed. It is not mandatory to have a signed response, but by default we enforce ...

    • 360Suite database configuration is not set when restarting Tomcat server

      Symptoms On application startup, a warning popup appears In the Administration console, the database configuration is empty even though is was setup previously Environment 360Suite Web Platform Linux server (all) Additional symptoms : tomcat logs In ...

    • Change Tomcat after 2025.1 upgrade

      Context To prepare for BI 2025 moving away from Java 8, we migrated from Java 8 to Java 21. This migration impacts everyone doing update from previous version, as the version used for Tomcat is not compatible anymore, as Java 21 requires a Tomcat 10 ...