Configure a Cloud-Based Directory
Table of Contents
Expand all | Collapse all
-
- cloud-identity-engine-attributes
- Collect Custom Attributes with the Cloud Identity Engine
- View Directory Data
- Cloud Identity Engine User Context
- Create a Cloud Dynamic User Group
- Configure Third-Party Device-ID
- Configure an IP Tag Cloud Connection
- Configure Dynamic Privilege Access in the Cloud Identity Engine
- Configure Security Risk for the Cloud Identity Engine
-
-
- Configure Azure as an IdP in the Cloud Identity Engine
- Configure Okta as an IdP in the Cloud Identity Engine
- Configure PingOne as an IdP in the Cloud Identity Engine
- Configure PingFederate as an IdP in the Cloud Identity Engine
- Configure Google as an IdP in the Cloud Identity Engine
- Configure a SAML 2.0-Compliant IdP in the Cloud Identity Engine
- Configure a Client Certificate
- Configure an OIDC Authentication Type
- Set Up an Authentication Profile
- Configure Cloud Identity Engine Authentication on the Firewall or Panorama
- Configure the Cloud Identity Engine as a Mapping Source on the Firewall or Panorama
- Configure Dynamic Privilege Access in the Cloud Identity Engine
-
- Get Help
Configure a Cloud-Based Directory
After you activate your Cloud Identity Engine tenant,
configure a cloud-based directory, such as Azure Active Directory
(Azure AD), Okta Directory, or Google Directory, to communicate
with the Cloud Identity Engine.
To use the System for Cross-domain Identity Management (SCIM)
provisioning to customize which attributes your Azure AD shares
with the Cloud Identity Engine, you can configure the SCIM Connector.
If the connection between your directory and the Cloud Identity
Engine is not active, you can reconnect your directory. If you no
longer want to associate a directory with the Cloud Identity Engine,
learn how to revoke the permissions for that directory.