Communication protection
The IDMS web API, web page, and client platforms all enforce mutually authenticated, encrypted connections for all transactions.Each transaction is governed and protected by SSL/TLS rules using the strongest cipher suites. The table below lists the different certificates that are used, and the respective location for each certificate.
|
ID |
Certificate Type/System |
Description |
Location |
|---|---|---|---|
|
1 |
SSL Certificate / Credential Management System |
Used by the Web Server that is hosting the CMS. This certificate provides a means for the client to verify the CMS server. |
IIS Web Server Store |
|
2 |
SSL Certificate / IDMS |
Used the by Web Server that is hosting the IDMS. This certificate provides a means for the client to verify the IDMS server. |
IIS Web Server Store |
|
3 |
Client certificate for IDMS to connect to CMS |
Used by the IDMS to connect to the CMS API. This certificate enables the CMS to verify the IDMS. |
Current User, Personal Store of the account the IDMS is configured to run as. |
|
4 |
Enrollment Agent for CMS to connect to CA (Microsoft CA Only) |
Used by the CMS |
Current User, Personal Store of the account the CMS is configured to run as. |
|
5 |
Client certificate for IdExchange connect to IDMS. |
Used by the IdExchange microservice to communicate with the IDMS. |
Local Computer, Personal Store of the server where the IdExchange Microservice is installed. |
|
6 |
Client certificate for operators to connect to the IDMS and CMS systems. |
Used by the CMS and IDMS systems to authenticate operators and administrators. |
On the PIV credentials of the badge holders. |
