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

Chapter 1: Introduction
Different Passwords in Staging and Production Domains
You can use unique passwords for access to each domain to control changes made to the
staging and production environments. For example, the domain used for developer
integration testing might have a password known to all developers, whereas the
administrators of the staging and production environments might have secret passwords.
As a result, the developer roles and administrator roles are distinguished by their access.
The Sonic Workbench development environment should not connect to or update a
deployment domain. Any required changes migrate from the development environment to
deployment, thereby honoring the life cycle stages.
Using Authentication to Differentiate Management Roles
Another approach to authentication control uses a variety of administrative user names so
that the authority to use administrative tools, ESB tools, management connections for
service containers, and management connections for messaging nodes can be assigned to
different authenticated users.
This technique can be particularly useful if you want to lock out most users of
management connections for administrative tools while importing and validating
deployments. When you are about to enter a deployment import session, you can check
that there are no user connections that are not intended to be involved in import sessions
and then temporarily change their user password until the deployment session has been
validated (or reverted). With this technique, management connections for services and
messaging nodes would not be impacted.
Important When domains use management permissions, specified actions might not be allowed and
some configuration objects might not be visible. See the chapter “Permissions to
Maintain Configurations and Perform Runtime Actions” in the Progress SonicMQ
Deployment Guide.
Connection Authentication
When you use ESB connections to messaging nodes with routing to other messaging
nodes, and security is enabled, these connections require user authentication as routing
users. The subset of users that you define for these connections can increase the
granularity of your control over access and minimize the recovery time from unauthorized
use of a user name and password.
28 Progress Sonic ESB Deployment Guide 8.5