Introduction to SA, SSO, and Third-Party Certificates

The SA, SSO and CI technical reference is for technical and management staff who need an overview of communication with IC with respect to Single Sign On using Third-party certificates instead of CIC certificates for secure communication.

SA is used to configure CIC Server in a new installation and to configure and install the certificates.

Single Sign-On is an industry term for using one instance of user identity authentication across multiple applications and systems. SAML SSO works by transferring the user’s identity from one place (the identity provider) to another (the service provider). This is done through an exchange of digitally signed XML documents.

The third-party certificates ensures that the corporate data is encrypted in such a way, that only the recipient who owns the certificate can decrypt it.

CIC provides many options to allow administrators to choose a necessary security level that is appropriate for each environment in which IC resides. IC enables many Pureconnect Security Features by default while other security features require licensing. Administrators enable and configure those features through one or more CIC applications.

All components of an IC System use asymmetric Public-Key cryptography and a form of Public-Key Infrastructure (PKI) with certificates to validate every connection between them. CIC Subsystems, such as Interaction Media Server, Session Manager, and Interaction SIP Proxy, use this security schema to validate connections with other subsystems, CIC client applications, and the IC server. The IC System validates most of these connections automatically without visual notifications and requires little to no configuration efforts by an administrator.