In this article, you’ll learn how to integrate your LDAP with an Acreto Ecosystem. The described procedure is universal for all LDAP services and requires knowledge about connection details. If you search for platform-specific guide you may want to read articles about Active Directory - Azure or Active Directory - Windows Server.
In this article we will use Okta as a free LDAP provider.
In order to integrate Acreto with the LDAP provider, you will need:
An LDAP integration allows your Acreto Ecosystem to utilize the user credentials stored in your LDAP to connect to the Ecosystem using the Acreto TLS Client.
We recommended using the LDAPS version of the protocol to establish communication between the Acreto Ecosystem and the LDAP service. This is a secured version of protocol, any modern LDAP service provider should support that.
Administrators integrate with an LDAP (Lightweight Directory Access Protocol) directory to streamline the user login process and to automate administrative tasks, such as creating users and assigning roles. An LDAP integration allows the system to use it’s existing LDAP server as the master source of user data.
Typically, LDAP integration is also part of a single sign-on implementation.
The integration uses the LDAP service account credentials to retrieve the user’s distinguished name (DN) from the LDAP server. Given the user’s DN value, the integration then reconnects with LDAP using the user’s DN and password.
In the diagram below, you can see the communication flow between some Employee (trying to connect to the Ecosystem using Acreto TLS Client), Acreto Ecosystem, and LDAP.
The integration never stores LDAP passwords on the Ecosystem.
The integration uses a read-only connection that never writes to the LDAP. The integration only queries for information.
To configure your LDAP to work with Acreto, please:
Log in to New or Existing Ecosystem
Create Security Policy Create a Security Policy that allows users to connect through your Identity Provider to reach all destinations.
To simplify the initial configuration, we will create a policy that allows all traffic to be passed through the Ecosystem.
You should customize the Security Policy to fit your needs once the Identity Provider setup is complete. It should be configured to limit access to network resources for each group (Profile Group).
Add New Identity Provider
To add a new Identity Provider, select Objects and Identity Providers from the left menu and then click on “Add New”.
Fill the form with proper values:
ou=users, dc=ACCOUNT-ID, dc=okta, dc=com
.
Base DN and other values may be specific for your custom configuration. Check proper configuration in the LDAP provider knwoledge base.
To allow users, employees, or team members VPN users to authenticate in Acreto Connect Client using LDAP credentials, Acreto offers unique and individual URLs for every Ecosystem portal called Onboarding Portal.
To access the unique URL to that portal, please click on Edit next to the previously added IdP and scroll down.
Then, click on the icon to copy the URL.
Now, provide the generated link to your users.
When the End User or Employee opens the Onboarding Portal, the Welcome Page will be presented.
The Ecosystem Admin should share this URL with the End Users, ask them to open it, and then follow the instructions.
Thanks to Acreto and LDAP providers, users can connect to an Acreto Ecosystem with the same credentials utilized for other internal resources on their network domain.
Also, Acreto Ecosystem Admin(s) can re-use any existing password and security policies that are already in place. For example, the LDAP provider may already have account lockout and password expiration policies.