Skip to main content

Required Integrations

Secfense IdP works in conjunction with the Secfense User Access Security Broker as its operational and configuration hub. Additionally, Secfense IdP allows customers to retain ownership of the user database that manages user authentication.

As such, the User Access Security Broker requires certain integrations with external services to enable this functionality.

Identity Provider cloud tenant​

A link to the cloud tenant created for this specific project is necessary. To create this link, request the tenant URL and refresh token from your Secfense representative. Once received, enter them into the global configuration and remember to regenerate the key

Identity Provider

Enabling this function makes it possible to configure remote applications within Applications section of the configuration. The guide on how to prepare a remote application reprentation is here

LDAP​

Integrating with an LDAP user database is required to verify user credentials during enrollment and to check user security groups during normal usage. You will need data from your Active Directory or any other LDAP server to configure this integration:

ldap integration

Microsoft Entra ID​

If you prefer to use Microsoft Entra ID as your IAM solution, this option is also available. Entra ID is contacted via an HTTPS API and can be added in the Microsoft Entra API Configurations. You will need the following information from your M365 account:

entra integration

Once configured, you can select the prepared configuration from the appropriate section within the IdP configuration:

entra selection