#Blocking stunnel password
#Blocking stunnel download

To use Apache Directory Studio, connect through stunnel and use an access credential (username and password) generated in the Google Admin console. To address this scenario, see Use stunnel as a proxy.Ĭonfiguration instructions for specific LDAP clients ADSI Edit (Windows) IMPORTANT: Some LDAP clients, such as Apache Directory Studio, don't support the uploading of digital certificates. If the LDAP client doesn’t provide a way to authenticate with a client certificate, see Use stunnel as a proxy. Use the certificate and key file downloaded from the Google Admin console. For instructions, see Generate access credentials.

#Blocking stunnel password

Generate a username and password in the Google Admin console.

If the username and password fields are not mandatory, you can skip this step. In addition to authenticating with a certificate, some LDAP clients require that you enter a username and password. Use the following table for basic connection information: Note: For complete details about how and where to upload TLS certificates, please see your vendor documentation. To begin the process of uploading the certificate to the LDAP client, open the LDAP client's authentication or directory settings, and enter the details from the table below.

The Secure LDAP service uses TLS client certificates as the primary authentication mechanism.

Upload the certificate to your LDAP client.

Configure your LDAP client with Cloud Directory as your LDAP server.

To connect the LDAP client to the Secure LDAP service: To make sure user authentication works correctly for such LDAP clients, you'll need to turn on Read user information for all organizational units where Verify user credentials is turned on. (For instructions, see Configure access permissions.) Note: Certain LDAP clients such as Atlassian Jira and SSSD perform a user lookup to get more information about a user during user authentication. If your LDAP client is not listed in the instructions below, be sure to consult the documentation for that application. This section includes generic instructions for connecting your LDAP client to the Secure LDAP service.

#Blocking stunnel download

These instructions assume that the client key and cert files that you download are called ldap-client.key and ldap-client.crt.

Optional: Use stunnel as a proxy-This section includes instructions that specify additional considerations when connecting LDAP clients that don't support digital certificates.

Configuration instructions for Java applications-Includes generic instructions for Java-based applications that offer LDAP functionality.

The steps vary depending on the type of client.

Configuration instructions for specific LDAP clients-Includes instructions for connecting specific LDAP clients (such as Atlassian Jira or OpenVPN) to the Secure LDAP service.

Basic configuration instructions-Includes generic instructions for connecting LDAP clients that are not specified in this article.

This article includes the following sections: For instructions, see Secure LDAP connectivity testing.Īfter connecting the LDAP client by following the instructions on this page, you'll need to complete the setup of your LDAP client by switching the service status to On in the Google Admin console. For instructions, see 5. Optionally, before you begin with these steps, you might want to do a quick connection test using simple tools like ldapsearch, ADSI, and ldp.exe. You can also use these tools for troubleshooting if you encounter errors while trying to connect your LDAP client to the service. In addition to these help instructions, be sure to read your vendor documentation for the most up-to-date steps for connecting your client to the Secure LDAP service.īefore using these instructions, make sure you have already added the client to the Secure LDAP service, configured access permissions, downloaded a client certificate and key, and optionally created access credentials. The details in this article for connecting your LDAP client to the Secure LDAP service are for reference only, and are subject to change.

Be sure to read your vendor documentation.

Use the instructions in this article to connect your LDAP client to the Secure LDAP service.