Communication happens using SSL (secured sockets layer) protocal in case user clicks on:
-
Library Server Parameters
-
Resource Managers
-
Authentication
-
Authorization
In IBM Content Manager architecture, SSL/TLS secures communication between clients and Resource Managers when accessing resources, protecting data in transit.
In this system (a content/library management platform), SSL-secured communication is specifically invoked when connecting through 'Resource Managers' — the component that brokers connections to back-end storage/content resources, which is why it's configured to use SSL for that channel. 'Library Server Parameters' concerns configuration settings, not live communication; 'Authentication' and 'Authorization' are access-control steps that may ride over an already-established connection but aren't themselves the trigger point named in this product's documentation for SSL usage. Without more product context this is a fairly narrow, tool-specific fact rather than general knowledge.