esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...

Updating Security
Updating Security
Security in a domain has a set of interdependencies that make it an important aspect of the
initial creation of a domain and messaging nodes. You should plan what security you will
use and implement the plan as you define the domain and messaging nodes.
There are many aspects of security to consider:
● When you use authentication, you must:
■ Consider whether to use external authentication and the login SPI.
■ Create the users and passwords in the default authentication domain, or use a
different authentication domain.
■ For SSL, configure the provider, acceptors, and—if you use certificates—the
certificate management and certificate revocation lists.
● When you use Quality of Protection, the cipher suite for encryption
● When you use authorization, defining authorization policies
See the SonicMQ Deployment Guide section on implementing security in a domain.
Note Channel Encryption and External Authentication — See the SonicMQ Deployment
Guide and the SonicMQ Configuration and Management Guide for details about SSL
parameters, HTTPS, QoP, and the Login SPI.
Reconciling Users and Groups to Authentication Domains
SonicMQ endpoint connections specify a user and password. You must either create the
user and password information in the target domain or change the ESB connection user
and password to one that exists in the target domain.
Reconciling Endpoint Access and QoP to Authorization Policies
Access control and Quality of Protection (QoP) is enforced by authorization policies in
the target domain. Unless you set up patterns that will apply appropriate policies to new
queues, topics, and routings, you must modify the ACLs in the target domain to provide
your preferred pattern of permissions.
Progress Sonic ESB Deployment Guide 8.5 131