Supported identity providers in Security Center
Third-party identity providers (IdPs) are validated against specific versions of Security Center using the protocols listed in the table.
An identity provider is required to implement third-party authentication in Security
Center. For more information, see What is third-party authentication?.
Supported identity providers
The following list of third-party identity providers are certified to work with Security Center.
| Identity provider | Authentication protocols | Supported Security Center versions |
|---|---|---|
| Active Directory Federation Services | 5.4 GA and later | |
| 5.7 SR2 and later | ||
|
5.9.2.0 and later | |
| Microsoft Entra ID |
|
5.9.2.0 and later |
| KeyCloak |
|
5.9.2.0 and later |
| Okta single sign-on | 5.9.3.0 and later | |
|
5.10.1.0 and later | |
| OneLogin single sign-on |
|
5.10.3.0 and later |
Identity providers supported by design
The following third-party identity providers are supported by design. This means they are standards-compliant and have been validated with some customers. However, we cannot guarantee full feature compatibility because no extensive testing has been done.
| Identity provider | Authentication protocols | Supported Security Center versions |
|---|---|---|
| CloudMinder |
|
5.9.2.0 and later |
|
5.9.2.0 and later Limitation: Google Identity Platform does not
support user group. A privileged user must manually assign the users to their
respective user groups in Security Center after an initial logon has been
attempted.
|
|
| PingFederate |
|
5.9.2.0 and later |
| PingOne |
|
5.9.2.0 and later |
| Shiboleth |
|
5.9.2.0 and later |
| SiteMinder |
|
5.9.2.0 and later |