Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
The Indeed Certificate Manager system can be integrated into other Indeed products – Indeed Access Manager and Indeed AM Enterprise Single Sign-On. Integration allows for combining the operations of smart card issue, certificate requesting and writing, as well as authenticator registration into a single process.
The smart cards issued in this way can be used both for authentication in domain and SSO applications and for digital signature or access to resources that require personal certificates. Integration between systems is possible at any stage, irrespective to what product has been deployed first. The setup of integration of Indeed CM and Indeed Access Manager& Indeed AM Enterprise Single Sign-On comprises two stages:
- Installation and setup of the required software
- Configuration of integration parameters
The first stage requires installation of the following components:
- Indeed-Id Administration Tools (or Indeed-Id Admin Pack) to each Indeed CM server
- Indeed-Id Extended Security Provider for each Indeed EA server
- Indeed-Id SmartCard + PIN Provider for each Indeed EA server
| Tip |
|---|
Indeed-Id Administration Tools is a part of Indeed-Id Enterprise Authentication system installation package. |
It is also necessary to setup the Extended Security Provider:
- Create Indeed-ID Enrollment Admins security group as per Installation and operation manual for Indeed-Id Extended Security Provider.
- Add service account (‘servicecm’) to Indeed-ID User Admins and Indeed-ID Enrollment Admins security groups.
The second stage requires setting of integration parameters in the smart card usage policy of Indeed Certificate Manager. Open the Indeed EA & ESSO section in the selected policy configuration and define the parameters for Indeed EA & ESSO (Table 3).
Table 3 – Integration parameters for Indeed EA & ESSO.
| Table auto |
|---|
| Parameter | Description |
|---|---|
Enable Indeed EA & ESSO integration | If enabled, there will be simultaneous issuance of smart card in the Indeed CM system and of authenticator "Smart card or USB token + PIN" in Indeed EA/ESSO systems. |
| Use Indeed EA proxy server | If enabled, the Indeed CM will address Indeed EA proxy, which, in turn, redirects the request to Indeed EA/ESSO servers. The proxy is mandatory, if the Indeed CM servers are beyond the domain of Indeed EA/ESSO system. |
| Proxy URL | The address of Indeed EA Proxy Server. |
Username Password | Credentials (username and domain password) of the user, which is a member of Indeed-ID User Admins and Indeed-ID Enrollment Admins security groups. |
Allow Enterprise Authentication usage | If enabled, then the user is allowed to use Indeed technology for authentication in domain using Indeed-Id Windows Logon component after a smart card issuance in the Indeed CM system. |
| Allow Enterprise SSO usage | If enabled, then the user is allowed to use Indeed technology for authentication in applications using Indeed-Id Enterprise SSO Agent component after a smart card issuance in the Indeed CM system. |
Generate windows account random password | If enabled, a random domain password is generated when a smart card is issued in the Indeed CM system. In this case, when current password expires, a new random one is generated, known only to Indeed EA system. |
Permissions for Enterprise Authentication, Enterprise SSO and random password generation are disabled, if the last registered user authenticator is removed.
| Info | ||
|---|---|---|
| ||
For example, if a user had no authenticator in the Indeed EA system and no cards in the Indeed CM system, then after issuance of a smart card with defined integration parameters this user would Indeed Certificate Manager have one authenticator ("Smart card or USB token +PIN") in the Indeed EA system and one card (for instance, eToken) in the Indeed CM system. If the smart card is deleted from the Indeed CM system, the authenticator in the Indeed EA is deleted as well, and, since there is no other trained authenticator, the permissions for Enterprise Authentication, Indeed-Id Enterprise SSO and random password generation are disabled (of course, if active at the moment of revocation). |