Before Security Center can use Azure Active Directory to authenticate users with OpenID Connect, setup is required in Config Tool and the Azure Portal.
This example shows the steps required to set up third-party authentication with Azure Active Directory (Azure AD) using OpenID Connect (OIDC) access tokens. The procedure is divided into the following sections:
To implement third-party authentication, you must have administrator rights in Security Center and Azure AD.
1 - Preparing Security Center
- Open Config Tool and connect to the Security Center main server as an administrator.
- In Config Tool, open
- In the Creating a role: Authentication Service window,
select OpenID and click
Next.
- Enter a name and optional description for the new Authentication Service role
and click Next.NOTE: If your system has multiple partitions, you can also add the new role to a specific partition here.
- On the Summary page, ensure all the information is correct, click Create, and click Close.
- In the newly created role, click the Network endpoint tab.
- On the Network endpoint page, copy the OIDC redirect
and logout URIs. These are needed to configure Azure AD.NOTE: You might need to restart the System task to see the endpoint URIs.
2 - Preparing Azure AD
- Have an Azure AD that represents your domain.
- Have provisioned at least one user.
- Have provisioned at least one user group that contains the users you want to grant access to Security Center.
- In the Azure Portal, open the Azure Active Directory for your tenant.
- In the left menu, select App registrations, and click
New registration.
- Enter a Name, select Single tenant
under Supported account types, and click
Register.
- In the left menu for your application, select
Authentication, click Add a
platform, and select Web.
- In Configure Web, enter the first redirect URI for
Security Center to
Redirect URIs and click
Configure.