Using My webMethods with ACL-Protected Broker Servers
If you are using My webMethods to manage a Broker Server that is secured with an access control list (ACL), you must assign an identity to the Broker user interface.
For basic authentication, an identity is composed of user name and password.
For SSL authentication, an identity is composed of:
A signed certificate, stored in a password-protected certificate file called a
keystore.
The trusted root of the certificate issuer (or authenticator), stored in a certificate file called a
trust store.
Note:
The ACL configuration of a Broker Server is deleted when you edit the SSL identity of that Broker Server. You have to reconfigure the ACL to include the newly edited Broker Server.
For information about assigning a basic authentication identity to the
Broker user interface in
My webMethods, see
Configuring a Basic Authentication Identity
for the
Broker User Interface Component.
For information about assigning an SSL identity to the
Broker user interface in
My webMethods, see
Configuring an SSL Identity for the
Broker User Interface Component.
Note:
If you do not configure an identity for the Broker user interface, or if you specify an identity that does not have administrative permissions for a particular Broker or Broker Server, you can still view some information about that Broker or Broker Server. You will not, however, be able to modify any settings or see all information of the protected resource.