Password Management Supported Platforms
Built-in Connectors
Password Manager comes with built-in connectors for the following types of platforms and supported systems:
|
Directories:
|
Servers:
|
Databases:
|
|
Any LDAP, AD, NDS, eDirectory, NIS/NIS+.
|
Windows 2000, 2003, 2008, Samba, Novell, SharePoint.
|
Oracle, Sybase, SQL Server, DB2/UDB, ODBC.
|
|
Unix:
|
Mainframes:
|
Midrange:
|
|
Linux, Solaris, AIX, HPUX, 24 more.
|
z/OS with RAC/F, ACF/2 or TopSecret.
|
iSeries (OS400), OpenVMS.
|
|
ERP:
|
Collaboration:
|
Tokens, Smart Cards:
|
|
JDE, Oracle eBiz, PeopleSoft, SAP R/3, Siebel, Business Objects.
|
Lotus Notes, Exchange, GroupWise, BlackBerry ES.
|
RSA SecurID, SafeWord, RADIUS, ActivIdentity, Schlumberger.
|
|
WebSSO:
|
Help Desk:
|
HDD Encryption:
|
|
CA Siteminder, IBM TAM, Oracle AM, RSA Access Manager.
|
BMC Remedy, BMC SDE, HP Service Manager, CA Unicenter, Assyst, HEAT, Altiris, etc.
|
McAfee, CheckPoint.
|
Flexible Agents Simplify New Integrations
(2)Password Manager includes a number of flexible connectors, each of which is used to script integration with a common protocol or mechanism. These connectors allow organizations to quickly and inexpensively integrate Password Manager with custom and vertical market applications. The ability to quickly and inexpensively add integrations increases the value of the Password Manager system as a whole.
There are flexible connectors to script interaction with:
|
API binding:
|
Terminal emulation:
|
Web services:
|
Back end integration:
|
Command-line:
|
|
|
|
|
|
Organizations that wish to write a completely new connector to integrate with a custom or vertical market application may do so using whatever development environment they prefer (J2EE, .NET, Perl, etc.) and invoke it as either a command-line program or web service.
If Hitachi ID Systems customer develops their own integrations, an effort of between four hours and four days is typical. Alternately, Hitachi ID Systems offers fixed-cost custom integrations for a nominal fee.
Password Synchronization Triggers
Transparent password synchronization can be triggered from native password changes on any of the following systems:
- Windows 2000/2003/2008 servers and Active Directory domains (password filter DLL on servers and/or DCs).
- z/OS mainframes with RACF, ACF2 or TopSecret security products (security exit in the LPAR with the security products).
- OS/400, iSeries servers.
- Unix servers (passwd program wrapper binary or PAM).
- Sun, Oracle and IBM LDAP servers (attribute change filter on the directory server).
Each of these triggers contacts the Password Manager server twice per password change, over an encrypted TCP/IP socket (shared key handshake, 128-bit AES encryption):
- First connection: validate password quality, possibly reject the user's choice of a new password and block the triggering password change due to policy violation
- Second connection: initiate transparent password synchronization





