Configure the Okta Privileged Access gateway
This topic explains how to configure a Okta Privileged Access gateway.
- Command-line options
- Configuration file
- Related topics
service: Runs the sft-gatewayd service
support: Collects local system information for Okta support
-h, --help: Displays help
-v, --version: Displays version
--syslog: Forces syslog logging
You can control Okta Privileged Access gateways by using a configuration file at /etc/sft/sft-gatewayd.yaml. After installing the gateway, an example configuration file is available at /etc/sft/sft-gatewayd.sample.yaml. If a configuration file hasn't been created or is unavailable, the gateway uses the following default values.
Restart the gateway before changes to the configuration file take effect. For details, see Manage the Okta Privileged Access gateway.
These options control how you add a setup token to your gateway. You must enable one of the following options. For details on obtaining a setup token, see Create tokens and labels.
|Specifies a setup token created on the Okta Privileged Access platform.
Note: If you use this option, the setup token remains available in plain text. Okta recommends restricting read permissions to the configuration file (for example, 0600 on Linux).
Specifies the path to a separate file containing the setup token. The default value is based on the operating system running the gateway.
This option is the recommended method.
If using this option, you must manually create the setup token file and add the setup token created on the Okta Privileged Access platform.
After the gateway is enrolled with a team, the gateway deletes the token file.
Note: If the
|Controls the verbosity of the logs. Okta recommends leaving this as
Valid values include:
|Specifies the network address (IPv4 or IPv6) used by clients to access the gateway. If no address is specified, the gateway uses the address indicated by the network interface or cloud provider metadata.
|Specifies the port clients can use to access the gateway.
|Specifies the network address (IPv4 or IPv6) used by the gateway to listen for connections. By default, the gateway listens for connections on every available interface.
|Specifies a port used by the gateway to listen for connections.
|Forces the gateway to use the bundled certificate store (instead of the OS certificate store) to secure HTTP requests with TLS. This also includes requests to the Okta Privileged Access cloud service.
Note: To use the OS certificate store, set this option to False.
|Controls whether the gateway accepts SSH and RDP proxy traffic. If enabled, SSH and RDP connection requests aren’t routed and the gateway won’t listen for proxy traffic requests.
|Specifies the URL of an HTTP CONNECT proxy used for outbound network connectivity to Okta Privileged Access. Alternatively, you can set the proxy using the HTTPS_PROXY environment variable.
These options control how the gateway establishes secure connections with LDAP servers.
By default, the gateway starts TLS, but doesn’t perform any certificate validation.
You must indent these options within an LDAP YAML dictionary using two spaces:
Warning: If StartTLS and UseLDAPS are set to False, then LDAP communications with Active Directory isn't encrypted. Okta recommends that you set StartTLS to True.
Upgrades Active Directory/LDAP server communications to TLS. If disabled, communication with the server isn't encrypted.
StartTLS is an extension to the LDAP protocol that uses the TLS protocol to encrypt communication. This option can't be enabled simultaneously with the UseLDAPS option.
Enables the use of the LDAPS protocol to encrypt communication. This option can't be enabled simultaneously with the StartTLS option.
If the UseLDAPS option is set to True, then this port value is used to make the LDAPS connection.
|Performs validation on certificates received from the AD/LDAP server. If disabled, LDAP server communications may be vulnerable to MITM attacks.
If enabled, the gateway looks for certificates at the path specified by
Teams should ensure that valid certificates for each connected domain are stored on the gateway before they enable this option. If no valid certificates are found, the gateway rejects all connections.
These options control how the gateway manages RDP sessions.
You must explicitly allow RDP connections with the
Enabled option and either the
Ubuntu 20.04, 22.04, RHEL 8, or RHEL 9 is required for RDP connections routed through a gateway.
Controls RDP functionality for the gateway. This option is disabled by default as RDP requires other configuration and must be set to True before any RDP connections are allowed.
|Restricts the gateway from validating server certificates when connecting to an RDP host. This flag is dangerous in non-test environments, but may be required if the RDP host has any self-signed certificates.
|Controls the number of concurrent RDP sessions allowed by the gateway. After reaching this number of sessions, other users will receive an error and be unable to connect to the gateway. This is done exclusively for resource and performance reasons.
|Controls the log level of RDP-internal logs. These messages are useful when diagnosing issues but might clutter logs.
Note: Set to False to label all internal RDP log messages as debug.
|Specifies a size threshold for session capture logs. After reaching this threshold, logs for an active session are signed and flushed to disk. This option must include a time unit (ms, s, m, h).
|Specifies a size threshold for session capture logs. After reaching this threshold, logs for an active session are signed and flushed. This option is measured in bytes.
|Specifies a temp directory to store SSH session logs before upload to the specified log destination.
The default depends on the operating system. On Linux, the default is /tmp, unless the $TMPDIR environment variable is specified.
The directories for the temporary and finalized session logs must be on the same device.
|Specifies where to store finalized session logs. Teams can store logs locally or on AWS or GCS buckets. You can store session logs in multiple locations. If doing so, the logs are sent to the destination in the order specified in the configuration file. Session logs are never sent to Okta Privileged Access.
See the following default values and examples.
Example - Linux/BSD
Gateways can't write to the
Example - AWS
Example - Google Cloud
System administrators can customize and configure the logFileNameFormats option to better understand and manage the session recording logs.