Technology
Hitachi ID Facebook Page Hitachi ID Twitter Page Find us on Google+ Hitachi ID YouTube Page

Hitachi ID Identity and Access Management Suite Server Requirements

Multiple, Load-Balanced Servers

Hitachi ID Identity and Access Management Suite supports multiple, load-balanced servers.

Each server can host multiple Hitachi ID Identity and Access Management Suite instances, each with its own users, target systems, features and policies.

Hitachi ID Identity and Access Management Suite instances can and normally do span multiple servers. Every server hosting a given instance is functionally identical. User traffic is load balanced between servers supporting the instance. Load balancing may be accomplished using DNS (round-robin is built into most DNS servers) or at the IP level with a device from Cisco, F5, etc.

High availability is accomplished by combining load balancing with server health monitoring and automatic fail-out. Hitachi ID Identity and Access Management Suite includes server monitoring tools that can be configured on each server to monitor its peers and when a failure is detected to trigger an alarm (e.g., by e-mail) and to automatically update DDNS records to remove the failed server from circulation. Hitachi ID Systems also provides these tools for Unix/BIND with traditional DNS.

There is no coded limit to the number of concurrent, replicated servers. In practice, with more than 10 servers, replication may become slow. Since the three largest customers of Hitachi ID Systems run with just two production servers each, this is only a theoretical problem.

Server Platform

Hitachi ID Identity and Access Management Suite must be installed on a Windows 2008R2 or 2012 server.

Installing on a Windows server allows Hitachi ID Identity and Access Management Suite to leverage client software for most types of target systems, which is available only on the "Wintel" platform. In turn, this makes it possible for Hitachi ID Identity and Access Management Suite to manage passwords and accounts on target systems without installing a server-side agent.

The Hitachi ID Identity and Access Management Suite server must also be configured with a web server. Since the Hitachi ID Identity and Access Management Suite application is implemented as CGI executables, any web server will work. The Hitachi ID Identity and Access Management Suite installation program can detect and automatically configure IIS or Apache web servers, but other web servers can be configured manually.

Hitachi ID Identity and Access Management Suite is a security application and should be locked down accordingly. Please refer to the Hitachi ID Systems document about hardening Hitachi ID Identity and Access Management Suite servers to learn how to do this. In short, most of the native Windows services can and should be removed, leaving a very small attack surface, with exactly one inbound TCP/IP port (443):

  1. IIS is not required (Apache is a reasonable substitute).
  2. No ASP, JSP or PHP are used, so these engines should be disabled.
  3. .NET is not required on the web portal and in most cases can be disabled on IIS.
  4. No ODBC or DCOM are required inbound, so these services should at least be filtered.
  5. File sharing should be disabled.
  6. Remote registry services should be disabled.
  7. Inbound TCP/IP connections should be firewalled, allowing only port 443 and possibly terminal services (often required for some configuration tasks).

Each Hitachi ID Identity and Access Management Suite server requires a database instance. SQL 2008R2 or SQL 2012 are the most common options, but Oracle database is also supported.

Application Server Hardware and Operating System

(1) Each Hitachi ID Identity and Access Management Suite server is configured as follows:

Database Configuration

In addition to a web/application server, Hitachi ID Identity and Access Management Suite requires a database server. In most environments, the database server software (Microsoft SQL Server or Oracle Database Server) is installed on the same hardware or VM as the Hitachi ID Identity and Access Management Suite software, on each Hitachi ID Identity and Access Management Suite server node. This reduces hardware cost, eliminates network latency and reduces the security surface of the combined solution.

Database I/O performance on a virtualized filesystem (e.g., VMDK or equivalent) may not be ideal. If a VM is used to host the database server software, please consider a NAS or SAN solution for disk I/O.

Hitachi ID Identity and Access Management Suite can leverage an existing database server cluster. Hitachi ID Systems recommends a dedicated database server instance, however, for a number of reasons:

  1. The data managed by Hitachi ID Identity and Access Management Suite is extremely sensitive, so it is desirable to minimize the number of DBAs who can access it (despite use of encryption).
  2. MSSQL and Oracle have almost zero ability to isolate workloads between database instances on the same server. This means that a burst of activity from Hitachi ID Identity and Access Management Suite (as happens during nightly auto-discovery) would cause slow responses in other applications. Conversely, other applications experiencing high DB load would slow down Hitachi ID Identity and Access Management Suite.
  3. Hitachi ID Identity and Access Management Suite already includes real-time, fault-tolerant, WAN-friendly, encrypted database replication between application nodes, each with its own back-end database. Use of an expensive DB server cluster is neither required nor beneficial.

The Hitachi ID Identity and Access Management Suite replicating data service can be configured to use any of the following SQL database engines as its physical data store:

While the database server may be 32 or 64 bit, a 32-bit DB client is currently required. Hitachi ID Systems will switch from 32-bit application server code to 64-bit server code once adoption of Windows 2008R2 becomes dominant among our customers. This will occur in release 9.0 of Hitachi ID Identity and Access Management Suite.