- Integrate an on-premise Active Directory (AD) as the Identity Repository.
We use "AD Connect" as an example, if you have integrated AD in other ways (e.g. LDAP directory), please skip this step.
- Add a new SAML application and configure the settings:
- Add a new SAML application, and specify the application name.
- Configure SAML Settings.
- Set the following values:
- Assertion Consumer Service (ACS): https://<host-to-your-ApexCentral>/WebApp/login.aspx
- Entity ID: https://<host-to-your-ApexCentral>/WebApp/login.aspx
- Signing: Sign Assertion
- Add new attribute with following settings:
- Set the Group Access.
- Make sure that the SAML settings are correct.
- Set the following values:
- Integrate AD with Apex One as a Service.
For detailed instructions refer to step 2 of Synchronize AD information and authenticate AD accounts from this article: Integrate Active Directory (AD) with Apex One as a Service. - In Apex Central, go to Administration > Account Management > User Accounts.
- Click Add.
- Select Active Directory user or group, specify the User/Group name, and click Next.
- Select the desired role, configure folder options, and click Save.
- Configure ADFS for Apex Central:
- Go to Administration > Settings > Active Directory and Compliance Settings > Active Directory Settings.
- Select the following:
- Enable Active Directory synchronization
- Enable Active Directory authentication
- Specify the SSO service URL and Service identifier, and select the Signing certificate:
Field Name on Apex Central setting page Ping Identity Attribute Name SSO service URL From SAML Metadata: Server identifier Single Sign-On (SSO) Relay State Server certificate Signing Certificate
- Switch to the Ping Dock and login as a user of the group granted with the access to the Apex Central service.
- Click the application to initiate SSO to Apex Central.
SP Initiated SSO
Enter an AD user in Apex Central login console, browser will redirect page to Ping. After authentication, the page will be redirected back to Apex Central.