Appendix B. ConnectionBuilder Methods
The following table outlines the key methods available to the ConnectionBuilder class used in V4 of the Java software development kit.
Table B.1. ConnectionBuilder Methods
| Method | Argument Type | Description |
|---|---|---|
|
|
|
The name of the user with which to connect to the Manager. You must specify both the user name and domain, such as |
|
|
| The password of the user with which to connect to the Manager. |
|
|
| Specifies whether responses from the server where the Manager is hosted should be compressed. This option is disabled by default, so this method is only required to enable this option. |
|
|
| The timeout, in seconds, to wait for responses to requests. If a request takes longer than this value to respond, the request is cancelled, and an exception is thrown. This argument is optional. |
|
|
|
The base URL of the server where the Manager is hosted. For example, |
|
|
|
The base URL of the SSO revoke service. This option only needs to be specified when you use an external authentication service. By default, this URL is automatically calculated from the value of the |
|
|
|
The token name in the JSON SSO response returned from the SSO server. By default, this value is |
|
|
| Enables or disables verification of the host name in the SSL certificate presented by the server where the Manager is hosted. By default, the identity of host names is verified, and the connection is rejected if the host name is not correct, so this method is only required to disable this option. |
|
|
|
Specifies the location of a file containing the CA certificate used to verify the certificate presented by the server where the Manager is hosted. This method must be used together with the |
|
|
|
The password used to access the keystore file specified in the |

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.