Skip to content
Cybersecurity & IAM

Cybersecurity & IAM

  • Allidm We are
  • Infographics
  • Privacy Policy

Configure New Directory in One Login – Integrating with Active Directory

Active Directory Connectors manage OneLogin user authentication against Active Directory and provide real-time synchronization of users between Active Directory (AD) and OneLogin. Active Directory Connectors also function as the redirect service in a Desktop SSO implementation.

Below the steps to configure the Active Directory within One Login.

Select Users | Directories | New Directory | Choose Active Directory

Login to the Server connected to your AD domain, and download the One Login AD Connector Version 5. Is important that you copy the token generated. This token number will be used during the AD connector installation.

Once downloaded double click on the file onelogin_ad_connector.msi to start the One Login AD Connector installation.

Accept the license agreement and click next.

Enter the installation token. This is the value provided during the download screen.

You have multiple options to run the connector service. Select Create One Login Service Account and click Next.

Installation creates the One Login Service Account.

Now you select the Port number, by default is 8080.

Now select the shard database

Now click install and One Login AD Connector 5 will start the installation.

Once completed, One Login AD Connector is ready and you can launch the domain configuration. Click finish.

At this point now you should be able to start configuring your AD domain at One Login and specify which domain or containers needs to be synced.

You will have the capability to add more features like:

  • Add Additional Active Directory Connectors for High Availability
  • Configure Desktop SSO with Active Directory Connectors

Share this:

  • Share on X (Opens in new window) X
  • Share on Facebook (Opens in new window) Facebook
  • Share on LinkedIn (Opens in new window) LinkedIn

Gabriel Magarino

Gabriel Magarino – Senior Security Manager | IAM Evangelist - Experienced leader with over 20 years in the IT and cybersecurity industry, specializing in Identity & Access Management. Expert in Okta, One Identity, SailPoint (IdentityIQ & IdentityNow), OneLogin, Delinea, and CyberArk. Passionate about exploring IAM and emerging technologies, coaching, and training IAM teams. Holds a Master’s in Computer Science and multiple certifications, including Okta Professional & Administration, One Identity Architect & Instructor, SailPoint Identity Now, ITIL, Scrum Master, among others. Currently pursuing a PhD with a focus on Computer Science and Artificial Intelligence.

Published On April 10, 2020

Post navigation

Previous PostOkta – Enabling Self-Service Registration
Next PostInstalling One Identity Manager Operation Support Portal

Recent Posts

  • Ping Identity Adds Agent Governance and Privilege to Its IAM Platform
  • Microsoft Is Killing SMS Authentication
  • Okta ISPM Integrates with Anthropic’s Claude Compliance API
  • Step-up authentication: the right friction at the right moment
  • PII in IAM: governing what identifies your users
  • The five identity categories every IAM program must govern
  • Why agentic identity is non-deterministic and why your IAM stack isn’t ready for it
  • What Makes a Company”AI Agent–Based”?
  • NHI-Agent Classification: A New Identity Model for AI-Driven Enterprises
  • Human vs machine identities: the two categories every IAM program must govern

Infographics

Latest Post

  • Ping Identity Adds Agent Governance and Privilege to Its IAM Platform
Copyright © All right reserved
Created By: Fansee Themes