Advanced Authentication architecture is based on the following three levels of architecture:
For more information, see Section 1.4.1, Basic Architecture
Enterprise Level Architecture
For more information, see Section 1.4.2, Enterprise Level Architecture
Enterprise Architecture With A Load Balancer
For more information, see Section 1.4.3, Enterprise Architecture With A Load Balancer
The basic architecture of Advanced Authentication is a simple configuration that requires only one Advanced Authentication server.
An Advanced Authentication server is connected to a directory such as Active Directory Domain Services, NetIQ eDirectory, Active Directory Lightweight Directory Service or other compliant LDAP directories. An Event Endpoint can be Windows, Linux or Mac OS X machine, NetIQ Access Manager, NetIQ CloudAccess, or RADIUS Client to authenticate through the RADIUS Server that is built-in the Advanced Authentication Server. For a complete list of supported events, see
In the enterprise level architecture of Advanced Authentication, you can create several sites for different geographical locations.
For example, the Figure 1-1 displays two Advanced Authentication sites, and
Figure 1-1 Enterprise Level Architecture
: The first site that is created for headquarters in New York. The first Advanced Authentication server of site A contains the and roles. This server contains a master database and it can be used to register new sites and servers.
: Another site created for the office in London. The structure of site B is similar to site A. The Global Master in another site has the DB Master role. DB servers interact with the DB Master.
provides a database that is used for backup and fail-over. You can create a maximum of two DB servers per site. When the Global Master is unavailable, the DB server responds to the database requests. When the Global Master becomes available again, the DB server synchronizes with the Global Master and the Global Master becomes the primary point of contact for database requests again.
Endpoints interact with Global Master or DB Master servers. When these servers are not available, they interact with DB servers.
NOTE:DB servers connect to each other directly. If the Global Master is down, the DB servers will replicate.
A Global Master must have a connection to each of the LDAP servers. Hence in a data center with Global Master, you must have LDAP servers for all the used domains.
Master servers do not initiate a connection to the DB servers. Master servers initiate connection to Master servers only. DB servers initiate connection to the DB Master of the same site and Registrar only.
IMPORTANT:Ensure to take regular snapshots or to clone the primary site to protect from any hardware issues or any other accidental failures. It is recommended to do it each time after you change the configuration of repositories, methods, chains, events and policies, or add or remove servers in the cluster.You can convert DB server of primary site to Global Master. This requires corresponding DNS changes. Nothing can be done if Global Master and all slaves are lost.
The enterprise architecture with a load balancer contains web servers and load balancers along with the components in Enterprise Level Architecture. Figure 1-2 illustrates the Enterprise architecture with a load balancer.
Figure 1-2 Enterprise Architecture with Load Balancer
serve more workload. It is not recommended to deploy more than 5-6 web servers per site.: Web server does not contain a database. It responds to the authentication requests and connects to Global Master. You need more web servers to
: A load balancer provides an ability to serve authentication requests from . A load balancer is a third-party component. It must be configured to interact with Web servers.
WARNING:Do not place the Advanced Authentication server in Demilitarized Zone (DMZ). It is recommended to use Load Balancer to process authentication requests from the external endpoints.
If a Global Master server (GMS) of a cluster goes down, the Web Servers of the primary site automatically communicate with the DB server of the primary site. When the GMS is up and running, DB server connects back to Web Servers. The switching happens within a few of minutes. If the DB Master server of a secondary site goes down, the Web Servers of the same site communicates to the DB Server of the same site. When the DB Master is up, Web Servers connect back to it. While a GMS is down, the replication between sites fail. While a DB Master of a secondary site is down, the site does not replicate with the Global Master server.
For information on the following see the respective link:
To restore the operations when a GMS is broken, see Restoring Operations When a Global Master Server is Broken.
To restore the operations when a DB Master of a secondary site is broken and when it is not possible to restore the DB Master, see Restoring Operations When a Database Master of the Secondary Site is Broken.
NOTE:To view an example of configuring a load balancer for an Advanced Authentication cluster, see