Configuring LDAP credentials - HubSpot/python-app-google-groups GitHub Wiki

Google Groups app works with both Microsoft AD servers and OpenLDAP servers. However, it requires bind credentials which will allow it to query all user's dn, proxyAddresses, SAMAccountName, displayName, and mail fields.

What is proxyAddresses and what is it used for?

Google Groups App requires a mapping of Slack user IDs to Active Directory accounts. This is achieved through a value in proxyAddresses indicating what each user's Slack ID is. Here is an example LDIF:

# Doe\2C John, Users, example.local
dn: CN=Doe\, John,CN=Users,DC=example,DC=local
proxyAddresses: slack:UABCD1234
sAMAccountName: jdoe

On startup, and periodically thereafter, Google Groups will load and cache all slack ID -> AD user mappings from your LDAP server.

You will need to run some other external tooling to build these mappings. A future improvement for this app may allow reading the email field from Slack instead, which would remove most of the need for an LDAP integration in the first place.

Configuring the app

Simply fill in the ldap section of the config with your own credentials. If you sync your AD users with your Google domain you may also want to use this account to create the Google project required for the Google credentials.