Overview
This chapter explains how to configure security for webMethods Broker clients by using the Broker C API. Information is provided that explains how to:
Authenticate
Broker clients using basic authentication
Authenticate
Broker clients using secure socket layer (SSL)
Manage SSL certificates for C client applications
Enable encryption
The Broker security model provides the following forms of protection for your event-based Broker C applications:
User authentication to verify the identity of a
Broker C client to the
Broker Server. The two-way SSL authentication verifies the identity of a
Broker Server to a
Broker C client attempting to make a connection
and that of the
Broker C client to the
Broker Server. Before making a connection, the basic authentication identity or the SSL identity must be assigned.
User authorization for
Broker objects protected by Access Control Lists (ACLs). Only clients whose basic authentication or SSL identities are specified in a
Broker object's ACL may connect to that object. This type of security protects confidential data from access by unauthorized users.
Encryption of the data traffic between a
Broker client and the
Broker Server, to protect sensitive data. Typically, you encrypt the data traffic when working with highly sensitive data, or to protect data of a confidential nature that passes across a public network. Encryption is supported for SSL enabled client. A basic authentication enabled client can also use the encryption only if the connection is SSL enabled.