Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Managing Broker Security | Access Control Lists | Configuring Access Control Lists
 
Configuring Access Control Lists
 
About Configuring Broker Server ACLs
About Configuring Client Group ACLs
About Controlling Which Brokers Can Join a Territory
About Controlling Which Brokers Can Join a Cluster
Setting Permissions to Connect to Remote Brokers across a Territory Gateway
About Setting Permissions to Connect to Remote Brokers across a Cluster Gateway
ACLs and Migration Issues
Once an ACL is enabled, only those users with identities listed in the ACL are granted access to the protected Broker object.
If a Broker object allows ACLs, you can configure a user ACL, an authenticator ACL, or both of these ACLs for the object.
You configure ACLs through My webMethods.
The following sections walk you through the steps for creating, configuring, enabling, and disabling ACLs for:
*The Broker Server
*A client group
*Remote Brokers in a territory
*Remote Brokers in a cluster
*Remote Brokers in a territory gateway
*Remote Brokers in a cluster gateway
Important:
For ACLs to work, basic authentication or SSL must be configured and enabled for the Broker Server. If you attempt to create ACLs on a Broker object without first configuring and enabling basic authentication or SSL for its controlling Broker Server, the Broker user interface will direct you to first configure basic authentication or SSL.