Universal Messaging 10.3 | Concepts | Deployment | Client | Client Security
Client Security
Universal Messaging makes use of JSSE for SSL enabled communication. Clients are able to connect using standard sockets (nsp), http (nhp), SSL enabled sockets (nsps) or https (nhps). Universal Messaging's client SSL communication uses the JVM's own SSL implementation.
Clients connecting using SSL (see Client SSL Configuration) will connect to a realm server that has an SSL enabled interface with either client authentication on or off.
Once authenticated using SSL, the client must have the desired permissions on the realm and its objects in order to perform the operations required. The entitlements are defined within the ACLs for the realm, channels, queues and services. The ACLs must contain the correct level of permissions for clients connecting to the realm.
Please also see the description of managing realm security ACLs in the documentation of the Enterprise Manager.