Integrating Your Password Manager With Azure Active Directory

Employees today need to access several different accounts throughout their daily activities, and it’s vital that the associated passwords are strong and secured to prevent data breaches. But how can employees be expected to remember lengthy and random passwords for all their logins? Hopefully, it’s already widely known that keeping passwords on sticky notes is a big no-no. Organizations should instead be using password managers, which are an easy way to maintain all necessary credentials stored safely in a vault protected by a master password.

LastPassThe Connection tab is where the administrator sets the connection between LastPass and the Active Directory by inserting the domain, credentials, and base DN.

The Actions tab contains all configurations regarding how to react when specific events occur in the company’s Active Directory. Although admins are free to configure the settings as they prefer, it’s advisable to disable accounts instead of deletingthem to prevent actions against user accounts, such as full vault data loss.

First of all, companies need an OAuth bearer token and an encrypted scimsession file to deploy the SCIM bridge, the location of which can be easily found on 1Password’s website. Once the admin has the necessary items, the application can be installed. 1P advises the use of a container, and offers dedicated guides for Google Cloud Platform, Azure Kubernetes Service, and DigitalOcean Kubernetes Service.

After the installation, administrators need to access their Microsoft Azure account to connect the identity provider to the SCIM bridge. To do so, they need to select ‘Enterprise application’ under the ‘Azure Active Directory’ tab in the sidebar, click ‘New application’, and click ‘Non-gallery application’. Here, admins can type the display name, select ‘add’, and the app is created. To configure the application, the admin has to go to the details page of the 1Password app just created and do the following:

RoboForm also offers AD integration through its RoboForm AD Connector. It can be downloaded from the user creation prompt in the company’s administrator console.

After installing the program and logging in with RoboForm’s admin account, insert the Active Directory admin credentials and specify the Base DN. The latter can also be left to be discovered automatically by RoboForm.

The next step is to select which of the Active Directory groups should be synced into the RoboForm for Business Company account and go over all the sync rules, which are pretty straightforward to set. The last two steps are to schedule RoboForm’s sync period and set the location where the RoboForm AD Client will store its logs.

When everything is done, the admin needs to press ‘Start’ so the software begins syncing. If there’s a need to change any of the settings, the admin just needs to click ‘Edit Configuration’.