The Lightweight Directory Access Protocol (LDAP) is an open, vendor-neutral, industry-standard application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network.
LDAP integration allows you to connect the instance to catalog service server with LDAP (for example, Active Directory) and user it as a source of the user data. It provides the ability to connect to a directory service storing the authentication data, such as usernames, passwords, user home directories used for keeping business and other data, etc. The global objective of the LDAP engine is importing users into the system. And through this, synchronization with various corporate services can be achieved, and one account can be used to authorize in all corporate services, such as email, website, VoIP, and so on.
The RDN (relative distinguished name) is the attribute defining the search directory, like this: dc=instance,dc=com
In this client-server infrastructure scheme, the SimpleOne instance has to be a client connecting to the LDAP server.
The users can authorize with user.ldap_autoprovision property that enables automatic creation of users in the User table in case the user is created in LDAP but not created on the instance.
When a user that has an account in the LDAP service catalog, but has not in the system, independently attempts to authorize, a user record is automatically created on the instance with a generated email in the format {random string of 10 characters}@simple.test.
|
You can also use third-party authorization services on your instance. See the Single Sign-On article to learn more.
The system synchronizes with the LDAP server only via the Schedule Jobs – scheduled script that defines periods of synchronization (for example, every 3 hours). See the Scheduled Script article to learn more. Thus, the data is not updated automatically at authorization or other operations.
To establish the connection between your SimpleOne instance and the LDAP server, complete the following steps:
Additional tools for setting up LDAP connection:
To configure an LDAP connection, complete the steps below:
LDAP Server form fields
Field | Mandatory | Description |
---|---|---|
Name | Y | Enter the server name. |
Root directory | Y | Enter the RDN of the search directory. Example: |
Active | N | Select this checkbox to make the server active. |
Username | Y | Specify the username authenticating the LDAP connection. |
Password | N | Specify the server password. |
If the RDN attribute is not specified, then the LDAP server will attempt to reach the server root directory during the authorization process. If the user logging in is not authorized to access this directory, the authorization process will be interrupted. |
In order to successfully connect to the server, the server and the current SimpleOne instance must be available for connection. Apart from that, the port to which you try to connect must be open.
The account used for connection must belong to the Domain User group. It means that the user must have the permission to read the catalog.
To create a URL, complete the steps below:
LDAP URL form fields
Field | Mandatory | Description |
---|---|---|
URL | Y | Enter the LDAP/LDAPS URL there. The SSL-certificate checks the domain, not IP-address, so the domain is used for connection. Example for LDAP:
Example for LDAPS:
|
Active | N | Select this checkbox to make the URL active. |
Order | N | Specify the order of this URL if there are more than one similar items. In this case, they will be processed in ascending order. |
Operational status | N | State of the LDAP connection. Available options:
|
Server | Y | Specify the appropriate LDAP server. |
If you need to establish a secure LDAP connection over SSL or LDAPS via port 636, provide the SSL certificate. If you do not have a valid certificate, the LDAP connection will be insecure. In this case, use port 389 (TCP/UDP).
To add an LDAP certificate, complete the steps below:
Attach the SSL-certificate file.
|
Certificate form fields
Field | Mandatory | Description | |
---|---|---|---|
Name | Y | Specify the record name to identify the certificate in the list. | |
Subject | N | The certificate attributes. This field is automatically populated based on the provided certificate data. For more information about these attributes, see the RFC 5280 documentation. | |
Issuer | N | The certificate issuer. This field is automatically populated based on the provided certificate data. | |
File path | N |
| |
Short description | N | Add a brief description for the record. | |
Active | N | Select this checkbox to activate the certificate. | |
Valid from | N | The date from which this certificate is valid. This field is automatically populated based on the provided certificate data. | |
Valid to | N | The date until which this certificate is valid. This field is automatically populated based on the provided certificate data. SimpleOne does not validate the value of this field but the connection will not be established if the certificate is expired. |
You can see the list of added certificates from the LDAP Server record form. To do so, click Certificates list. |
After you configured an LDAP server and an LDAP URL and performed all necessary customer infrastructure preparations, set up an LDAP setting.
If you completed the steps above and performed all necessary customer infrastructure preparations, proceed to setting up an LDAP setting.
To configure the LDAP setting, complete the steps below:
You can check the LDAP structure by clicking the Browse LDAP on the corresponding LDAP Server record.
Ensure that the connection is set up by performing the following steps:
If an error occurs, check LDAP Log records.
Import all necessary data from your LDAP server to the instance.
To complete the data import using LDAP, set up the following system elements:
The scheme below illustrates the process of data import from an LDAP server.
See the LDAP Import Source article to learn more.
The "out-of-the-box" solution contains an example of the connection to the Active Directory (AD) service.
Check out the examples mentioned below before setting up the LDAP import on an instance. The settings of the examples are protected from changes. In the hamburger menu of each record, click Make a copy to copy the example setting and change their values.
The following records are created and configured:
the SimpleOneCourses1 and SimpleOneCourses2 LDAP Settings. Use one of these definitions as an example to create a working connection with the AD service.
|
To connect and import the users from the AD service, complete the following steps:
If an error occurred in the system, you can check the log messages to find the cause. In the LDAP Log, you can find records of failed authorization attempts or attempts to bypass authorization policy. In fact, all these messages are recorded into the Main Logs (sys_log) table.
To see the LDAP logs, navigate to LDAP → LDAP log.
LDAP Log form fields
Field | Description |
---|---|
Source | Displays the source from where this log record comes from (LDAP Authorization or LDAP Autoprovision, as an example). |
Message | The log record message text. |
Level | This field specifies the error level. Available options:
|
Username | Reference to the user initiated this record creation. |
Some LDAP features can be configured on the client side using system properties. Available properties can be found in the LDAP Properties article.