Authenticate with local LDAP

In this article, we will expose solutions to benefit from your local LDAP authentication on your GLPI Network Cloud instance.

Opening your local directory

To benefit from your local LDAP directory, it is necessary to make it accessible from Internet.

That passes by the installation, on your infrastructure, of protocol LDAPS what will allow your directory LDAP and your instance GLPI Network Cloud to communicate in a protected way.

According to your infrastructure, it is also interesting to set up filtering to guarantee that only your instance GLPI Network Cloud can attack your LDAP directory from outside. ( IP address of your instance here )

1. You must prepare your environment for the use of the LDAPS protocol;

   1. LDAPS protocol enabled/accepted (depending on your environment);

   2. Port 636 open/accepted on your network from Internet/your GLPI Network Cloud instance.

2. You can finally configure the LDAP(S) authentication in your GLPI Network Cloud instance.

Synchronize your local directory on a Cloud directory (Azure AD)

This adds an intermediary and requires more configuration but allows you to benefit from your local directory if you do not want to expose it directly.

1. Subscribe to Azure AD

2. Synchronize your local directory with Azure AD;

3. Choose an authentication method for your GLPI Network Cloud instance (LDAPS or Oauth SSO -> our guide).

Dedicated VPN via the subscription of a GLPI Network Cloud Private offer

Subscribing to a GLPI Network Cloud Private offer will allow you to call upon our team to set up a dedicated VPN between your GLPI Network Cloud instance and your infrastructure.

1. Subscribe to a GLPI Network Cloud Private offer;

2. Migration or deployment of your private instance;

3. Ask for the implementation of a dedicated VPN;

4. Planning / Implementation / Validation of the VPN with a technician of our team.