Tutorial: Configure Google Secure LDAP with Access Server
Overview
The following points are crucial for integrating Access Server with Google LDAP.
Unlike most LDAP integrations, Google LDAP requires an SSL certificate rather than creating a Bind user, making the integration slightly more complex.
You will need to be familiar with the sacli tool for advanced configuration of Access Server.
An installed Access Server.
Access Server console and get root privileges.
Sign in to the Google Admin console.
Click Apps > LDAP. Or select Apps from the hamburger menu and choose LDAP.
From the LDAP app, click Add Client.
Name your client, enter an optional description, and click Continue.
Configure access permissions.
Once you've chosen permissions, click ADD LDAP CLIENT.
Your LDAP client starts in an OFF status and needs to be turned on.
From the Client Details page, change Service status to ON.
Click Edit details.
Choose the radio button for ON for everyone.
Click SAVE.
Now that you’ve started your new client, you need to add the certificate and key to your Access Server:
You can download the generated certificate (from the link on the confirmation page or the client’s details page). The certificate and key are in a ZIP file.
We suggest renaming these files and will refer to them as gldap.crt and gldap.key.
Upload your certificate to your Access Server in this directory: /etc/ssl/certs/.
Upload your key to your Access Server in this directory: /etc/ssl/private/.
Next, you need to ensure that Access Server has the rights to read this file by executing these commands:
chown openvpn_as:openvpn_as /etc/ssl/certs/gldap.crt chown openvpn_as:openvpn_as /etc/ssl/private/gldap.key chmod 644 /etc/ssl/certs/gldap.crt chmod 640 /etc/ssl/private/gldap.key
Configure the Google LDAP integration with Access Server using the sacli tool.
Connect to your Access Server's console and get root privileges.
Enter the following commands:
sacli --key "auth.ldap.0.name" --value "Google Secure LDAP" ConfigPut sacli --key "auth.ldap.0.server.0.host" --value "ldap.google.com:636" ConfigPut sacli --key "auth.ldap.0.use_ssl" --value "always" ConfigPut sacli --key "auth.ldap.0.ssl_verify" --value "internal" ConfigPut sacli --key "auth.ldap.0.ssl_auth_cert" --value "/etc/ssl/certs/gldap.crt" ConfigPut sacli --key "auth.ldap.0.ssl_auth_key" --value "/etc/ssl/private/gldap.key" ConfigPut sacli --key "auth.ldap.0.min_ssl" --value "tls1_2" ConfigPut sacli --key "auth.ldap.0.sasl_external" --value "true" ConfigPut sacli --key "auth.ldap.0.uname_attr" --value "uid" ConfigPut sacli --key "auth.ldap.0.users_base_dn" --value "OU=Users, DC=example, DC=com" ConfigPut sacli --key "auth.module.type" --value "ldap" ConfigPut sacli startReplace
DC=example, DC=comwith your Google LDAP domain name.
If the configuration is successful, the server will return “WILL_RESTART [‘client’]” as part of the return message. This indicates the server is now configured and ready to accept LDAP-authenticated connections.
If you receive an ERRBACK message, please ensure you are using the latest version of Access Server and try again. Here is information on how to update your version.
Sign in to the Admin Web UI.
Note on the Status Overview that Default authentication system now states ldap.
Click Users to add users. You can also create groups through your Google Workspace account and align those with Groups at that access control level.