The availability domain the outbound connector is in. May be unset as a blank or NULL value.
Example: {@code Uocm:PHX-AD-1}
The OCID of the compartment that contains the outbound connector.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}
A user-friendly name. It does not have to be unique, and it is changeable. Avoid entering confidential information.
Example: {@code My outbound connector}
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {@code {"Department": "Finance"}}
The OCID of the outbound connector.
The current state of this outbound connector.
The date and time the outbound connector was created in RFC 3339 timestamp format.
Example: {@code 2016-08-25T21:10:29.600Z}
Outbound connectors are used to help File Storage communicate with an external server, such as an LDAP server. An outbound connector contains all the information needed to connect, authenticate, and gain authorization to perform the account's required functions.