There does not appear to be a place where the configuration of Gluu with an Active Directory integration is clearly laidout. The videos refer to it, but you don't see the configuration all in one place. This is a configuration that does the following: A Gluu server is installed on the same network as the Domain Controller. GLuu Cache Refresh is configured to import users from AD. Then Gluu is configured to authenticate against AD. This is the same thing that occurs in the videos for configuring Cache Refresh. First, start in the Customer Backend Key/Attibutes tab for CR. For the key attribute put sAMAccountName. Add the source attributes cn and sn. (These appear to be the minimum necessary to make this work - with only cn, the log was showing an LDAP mapping error)  Next, configure the Source Backend LDAP Servers. For AD, the port is 389, and you will have to navigate and translate your AD tree to get the values for your bind DN user (this user is in the top level Users container in AD) and your base DN - but likely it is CN=domainame,CN=com. Make sure there are no spaces between the comma and the entry - that seems to be a problem.  Then go to the Cache Refresh tab and add the source attribute mappings and your server ip (this is your Gluu server ip).  It will take a bit to import from AD but you want to see something in the Last Run and other entries - more than 0 on the Updates on the first run. Once you have the users imported, you can change your authentication for Gluu to use the AD server rather than the Gluu LDAP. In the video this is done and the admin user can no longer login - and an external LDAP user (and in this case, and AD user) can login. **NOTE:** The presenter stays logged in with admin and tests with a new browser - this is important!!! If you somehow have AD not quite right, you won't be able to get back in. As long as you stay logged in with admin you can continue to admin. Another good idea would be to make the user that you log in with a member of the Gluu Manager Group - that way you can still admin it when you log in! So, that being said, go to Manage Authentication and change the LDAP configuration. It should look very much like the configuration for the Backend Server.  This configuration works - it imports from AD, and then you can authenticate when logging into Gluu with your AD user. I tested changing passwords and adding new users in AD. I did note some "fiddliness" - not sure if it was user error or if some things just took a little while to work. Sometimes I would set up a configuration and update, it would error in the log, then I would change it back, then re-set it up, and then it would work.