How it Works—BoKS Access Control & Authentication Infrastructure
Your organization probably has an electronic company directory. It is likely either Active Directory from Microsoft, or one from another vendor based on the LDAP protocol. The first piece of BoKS infrastructure, the BoKS Master, synchronizes with your existing directory, acquiring users, user groups, servers, business information, and what HR departments are now calling "entitlements".
The BoKS infrastructure supplements this data, attaching access policies derived from the combinations above. This matches the view of industry analysts, who advise you to separate the creation of employees and contractors (usually fed by your HR systems) from the application of security policy (managed by your security team) for authentication and access control requests.
To scale up the authentication infrastructure, and serve all the access requests forecasted by your architects or administrators, your security team can add the appropriate number of BOKS Replicas. Each additional node holds a complete copy of the security database so that an end user's authentication request can be satisfied by any BoKS Replica. Communication between Master and Replicas is highly efficient, keeping all information in sync.
In the event of a BoKS Replica node failure, others in the set will continue to answer authentication requests. If the BoKS Master server fails, IT operations can shift the role of BoKS Master to another BoKS Replica (either automatically or manually).
Want to Know More About How BoKS Enterprise Access Control Management Works?
