Adselfservice Plus Solution Architecture
Adselfservice Plus Solution Architecture
Adselfservice Plus Solution Architecture
Solution
Architecture
Scope of this document
This document provides a detailed look into the ManageEngine ADSelfService Plus architecture and
deployment options. After reading this document, you will have a good idea of the various
components that are needed to deploy ADSelfService Plus, the purpose of each component, and
how they communicate with each other to enable the various features of ADSelfService Plus.
In case you are configuring a high availability environment, you will need a primary
server and a secondary server. Both servers need to have ADSelfService Plus installed.
Refer to the high availability configuration here.
To enable load balancing, a primary server and one or more secondary servers have to
be configured. All the servers need to have ADSelfService Plus installed. Learn more
about load balancing configuration here.
Learn more about the hardware and software requirements to install ADSelfService
Plus.
1
Database
ADSelfService Plus uses a database to store information like Active Directory (AD)
attribute details, audit data, product configuration data, enrollment data, etc. The
product comes with a built-in PostgreSQL database. You can also use a standalone MS
SQL database or PostgreSQL database. Check out this guide for the steps to migrate
from the inbuilt PostgreSQL database to a standalone MS SQL database.
Admin portal: The admin portal lets the IT administrator of the solution configure
domain and connection settings (SSL, proxy server, etc.), create and apply various
policies, deploy MFA, integrate on-premises and cloud applications with password
sync and SSO, and do much more. Click here to learn how to access the admin portal.
User portal: The user portal lets the users enroll themselves in ADSelfService Plus,
perform the various self-service actions, search for employees, view the organization
chart, etc. The methods to access the user portal are explained in
this guide.
2
Optional components and prerequisites
The login agent can either be pushed onto the client computers using the admin portal,
Active Directory GPOs, Microsoft System Center Configuration Manager (SCCM),
third-party endpoint management solutions like ManageEngine Desktop Central, or be
installed manually. Refer to the links to know more about the ADSelfService Plus login
agent and its installation.
With the app, users can also authenticate themselves using a MFA method like
time-based one-time-passcode, push notifications, fingerprint-based, and QR codes.
The mobile app can be either manually installed by users or pushed to mobile devices
by the IT administrator.
3
Integrate with enterprise applications
Through password synchronization and single sign-on, ADSelfService Plus integrates
with various enterprise applications such as Google Workspace, Salesforce, Microsoft
365 (formerly Office 365), and Dropbox. When password synchronization is enabled,
any change to users' domain passwords is synchronized across all the integrated
applications, enabling the user to access all of them with a single password. In the case
of SSO, if the user has logged into their ADSelfService Plus account, they are
automatically logged into these cloud applications without having to furnish their user
credentials.
Active Directory
Password & Directory Password Expiry Password Policy Password MFA Endpoint
VPN server
Self-Service Notification Enforcer Sync & SSO Security
VPN
(Green) HTTPS
(Blue) LDAPS/LDAP
4
3. Deployment scenarios
Here are five scenarios that illustrate the various methods of ADSelfService Plus deployment:
It is standard to deploy ADSelfService Plus in the intranet of the organization. In this method, the
ADSelfService Plus web portal, login agent, and mobile application can only be accessed when the
user is connected to the intranet. Below is a depiction of ADSelfService Plus deployment over the
intranet:
LAN
When ADSelfService Plus is deployed over the internet, end users can log into the ADSelfService
web portal and mobile app through any external network. It is recommended that the internal
network with the ADSelfService Plus server, database, and other entities deployed is shielded from
client access through the internet using DMZ or reverse proxy. Here is an illustration of ADSelfService
Plus deployment over the internet:
5
ADSelfService Plus ADSelfService Plus
Integrated cloud apps
web portal/login agent mobile app
Active Directory
LAN
This guide provides the steps for securely hosting ADSelfService Plus over the internet.
a. DMZ setup
A DMZ is a sub-network that prevents clients from directly accessing the server, and therefore, the
internal LAN where the server and other components are deployed. The DMZ acts as a barrier
between the internet and the internal LAN where the ADSelfService Plus server, database, and AD
are located.
Active Directory
ADSelfService Plus
Reverse
Internet Server
Proxy (Tomcat server)
Firewall Firewall
DMZ
Database server
LAN
Here, the DMZ setup consists of a reverse proxy that is flanked on both sides by a firewall. The first
firewall is configured only to allow traffic from the internet to the reverse proxy, and the second
firewall is configured only to receive connections from the organization's LAN to the reverse proxy.
6
b. Reverse proxy
A reverse proxy is a type of proxy server that retrieves resources on behalf of a client from a server.
These resources are then returned to the client, appearing as if they originated from the reverse
proxy itself. Thus, the website or service never needs to reveal the IP address of its origin server.
Reverse proxy conceals the ADSelfService Plus server, the other components, and the LAN they are
located in from third-party attacks.
Reverse
Internet Proxy
ADSelfService Plus
Active Directory Server Database server
(Tomcat server)
LAN
Here, the reverse proxy has been placed behind the firewall that secures the LAN. When an inbound
request to the ADSelfService Plus server arrives, the reverse proxy intercepts and sends the request
to the server. It then fetches the response and sends it to the client on behalf of the server.
For more information, take a look at the guides on setting up a reverse proxy for ADSelfService plus
using AD360, Apache HTTP server, and Microsoft IIS.
3. High availability
High availability is configured in ADSelfService Plus to provide failover in the case of system or
application failures. High availability is achieved through automatic failover, that is, when the service
running on one server fails, another instance of the service running on another server will take over.
This illustration shows the architecture of the ADSelfService Plus environment when high availability
is configured:
7
Standby Standby
Active Directory
server
Web
Interface
When the primary server fails to function, the instance running in the secondary server takes over.
Since the data in the primary server is cloned to the secondary server during configuration, the
switchover is automatic and free of problems. High availability helps the IT administrators and end
users have continued access to ADSelfService Plus.
4. Load balancing
With load balancing, the incoming requests to ADSelfService Plus are split among multiple server
nodes. To enable load balancing in ADSelfService Plus, a primary node and multiple secondary
nodes have to be configured. Here is how the primary node and secondary nodes are placed in the
ADSelfService Plus architecture:
Node 1
Active Directory
Node 2
Web Load
Interface Balancer
Node 3
Database server
Node 4
When requests are made to ADSelfService Plus, the primary node directs splits the requests among
the secondary nodes using the round-robin method. Load balancing helps alleviate performance
degradation due to heavy traffic and improves user experience.
8
These scenarios explain various ways that ADSelfService Plus can be deployed in a network. If you
need help deploying ADSelfService Plus, contact us at [email protected].