Everything You Need to Know About Azure and Active Directory Landscape
It uses legacy authentication protocol such as LM, NTLM and Kerberos. Active Directory provides full administrative control.
+1 (805) 480-9300
|
Offers & Trials
-
-
- Dutch
- English
- العربية
- Español
- Français
A Single Interface
to Manage Multiple Data DirectoriesA directory service is the part of a distributed IT environment that provides the necessary data to identify, locate and access the users and resources available on the network.
Most enterprises today already have multiple data directories with scattered authentication (AuthN) and authorization (AuthZ) data distributed across various geographies and networks that cause many challenges for applications/systems to authenticate and authorize end-users, systems, and services.
ORSUS Directory Services (ODS) provides a single, consistent, unified interface that enables a consolidated view of Authentication and Authorization data by syncing the user and entitlement access data from multiple directories into its own unified directory.
ODS gives you a virtual view of multiple Directories, supporting all the LDAP operations, including proxying of the bind requests over to the respective backend Directories.
ODS Features
The ORSUS Directory Services has
two major components
ORSUS Directory Server
This is an LDAP Directory where the user and entitlement data from multiple directories is consolidated and synced periodically. The enterprise applications connect to this directory for authentication and authorization purpose. Authentication requests are proxied over to the backend directories, so passwords don’t have to be replicated.
ORSUS Directory Proxy
This is a directory that gives a virtual view of multiple backend directories. All LDAP calls, including the binds, are proxied over to the backend directories.
Why
ORSUS Directory Services?With the help of ODS, the Applications/Systems do not have to reach out to multiple data Directories that the organizations may have distributed over different geographies.
- Single Directory containing AuthN and AuthZ data.
- Proxies bind requests to the respective backend Directory for credentials still managed in backend Directories.
- Replicates AuthZ data from multiple Directories, hence reducing latency for Applications/Systems consuming this data.
- Horizontally scalable to meet performance requirements.
- Extensible across multiple geographies closer to the Applications/Systems connecting to the ODS.
Related Resources
Let’s
Get Started NowExplore and experience how ODS can be configured to use a single Directory to view of Authentication and Authorization data from multiple data directories.
-
