One Identity Safeguard for Privileged Sessions 6.9.4 - REST API Reference Guide

Configures Source Network Address Translation. Possible values are:

• box_address

  Default. Uses the network address of the logical interface of SPS.

• original

  Uses the IP address of the client, as seen by SPS.

• fix

  Uses a fixed address when connecting to the remote server.

  Must be used with the address element.

Must be used if the value of the selection element is set to fix.

The IP address to use as the source address in server-side connections.

Collection of access policies. Access policies define who can authorize and audit a connection.

References the identifier of the indexing policy. You can configure indexing policies at the /api/configuration/policies/indexing/ endpoint.

To modify or add an indexing policy, use the value of the returned key as the value of the policy element, and remove any child elements (including the key).

Specifies the indexing priority for the connection. Possible values are:

• 5

  Very low priority.

• 4

  Low priority.

• 3

  Normal (default) priority.

• 2

  High priority.

• 1

  Very high priority.

• 0

  Near real-time priority.

Set to true to log audit trail downloads.

Retention time, in days. Must not exceed the retention time of the archive_cleanup_policy, and the retention time configured in the global settings of the protocol.

The global settings of the HTTP protocol are available at the api/configuration/http/options endpoint.

Specifies the verbosity level of sessions handled by this connection policy. The log level of other connection policies is not affected. If disabled, the log level set at the /api/configuration/<protocol>/options endpoint is used.

• To use the default log level, disable this option:

  "override_log_level": {
      "enabled": false
  },

• To use a custom log level for the connection policy, enable this option and set the log level to use:

  "override_log_level": {
      "enabled": true,
      "log_level": 5
  },

References the identifier of the channel policy. The value of this option cannot be null.

To modify or add a channel policy, use the value of the returned key as the value of the channel_policy element, and remove any child elements (including the key).

You can configure HTTP channel policies at the /api/configuration/http/channel_policies/ endpoint.

References the identifier of the settings policy. The value of this option cannot be null.

To modify or add a settings policy for this protocol, use the value of the returned key as the value of the settings element, and remove any child elements (including the key).

You can configure HTTP settings policies at the /api/configuration/http/settings_policies/ endpoint.

Cannot be null.

References the identifier of the audit policy. You can configure audit policies at the /api/configuration/policies/audit_policies/ endpoint.

To modify or add an audit policy, use the value of the returned key as the value of the audit_policy element, and remove any child elements (including the key).

References the identifier of the LDAP server. You can configure LDAP servers at the /api/configuration/policies/ldap_servers/ endpoint.

To modify or add an LDAP server, use the value of the returned key as the value of the ldap_server element, and remove any child elements (including the key).

References the identifier of the backup policy. You can configure backup policies at the /api/configuration/policies/backup_policies/ endpoint.

To modify or add a backup policy, use the value of the returned key as the value of the backup_policy element, and remove any child elements (including the key).

Cannot be null.

References the identifier of the authentication policy. You can configure authentication policies at the /api/configuration/http/authentication_policies/ endpoint.

To modify or add an authentication policy, use the value of the returned key as the value of the authentication_policy element, and remove any child elements (including the key).

References the identifier of a Usermapping Policy. You can configure Usermapping Policies at the /api/configuration/policies/usermapping_policies/ endpoint.

To modify or add a Usermapping Policy, use the value of the returned key as the value of the usermapping_policies element, and remove any child elements (including the key).

References the identifier of the archive/cleanup policy. You can configure archive and cleanup policies at the /api/configuration/policies/archive_cleanup_policies/ endpoint.

To modify or add an archive/cleanup policy, use the value of the returned key as the value of the archive_cleanup_policy element, and remove any child elements (including the key).

Configures a DNS server that is used to reverse-resolve the hostname if the Channel Policy contains the address of the target as a hostname instead of an IP address. By default, this is disabled and SPS uses the DNS server set in the /api/configuration/network/dns endpoint.

• To use the default DNS, disable this option:

  "server_address": {
      "custom_dns": {
          "enabled": false
      },
      ...
  },

• To use a custom DNS, enable this option and set the IP address of the domain name server to use:

  "server_address": {
      "custom_dns": {
          "enabled": true,
          "server": "192.168.1.1"
      },
      ...
  },

Configures the address where the clients connect to. Possible values are:

• original

  Connect to the same address specified by the client.

• nat

  Perform a network address translation on the target address.

  Must be used with the network element.

• fix

  Must be used with the address and port elements.

• inband

  Extract the address of the server from the username.

  Must be used with the domains element.

  Optional elements: exception_domains, dns_server, and dns_suffixes.

Can only be used if selection is set to inband.

IP address or the hostname of the domain name server used to resolve the address of the target server.

Can only be used if selection is set to inband.

If the clients do not include the domain name when addressing the server (for example they use username@server instead of username@server.example.com), SPS can automatically add domain information (for example example.com).

You can add multiple domain names. SPS attempts to resolve the target address by appending the domain names in the provided order, and uses the first successfully resolved address to establish the connection.

Must be used if selection is set to inband.

Specifies if the target address range is provided as a domain or as an IP range. Possible values are:

• address

  The value of the target address is an IP range.

• domain

  The value of the target address is a domain.

The address range of the target server(s).

Use the selection element to specify if the address is an IP range, or a domain.

Can only be used if selection is set to inband.

Lists the address ranges that are excluded from the connection policy.

Specifies if the excluded address(es) are provided as a domain or as an IP range. Possible values are:

• address

  The value of the excluded address is an IP range.

• domain

  The value of the excluded address is a domain.

The excluded address(es).

Use the selection element to specify if the address is an IP range, or a domain.

Configures the encryption used in the sessions.

• disabled: Use unencrypted web proxy connection between the HTTP client and .

  "transport_security": {
      "selection": "disabled"
  },

• tls: Enables TLS-encryption.

  "transport_security": {
      "selection": "tls"
  }

Selects the certificate to show to the peers. You have the following options:

• Use the same certificate for each connection:

  Select this option if you want to use the same certificate for each connection. Note that you must reference a certificate that includes its private key that you have already uploaded to SPS. For details, see Certificates stored on SPS.

  "host_certification_method": {
      "selection": "fix",
      "x509_identity": "893b7eb7-8c6f-403a-ba3a-1d09dc4b4c7a"
  }

• Generate a certificate for the target requested by the client:

  Select this option if you want to generate a certificate for the target requested by the client. Note that you must reference a Signing CA that you have already configured on SPS. For details, see Signing CA policies.

  "host_certification_method": {
      "selection": "generate",
      "signing_ca": "1904188625a843f11d30a5"
  },

Possible values:

• fix: if you want to use the same certificate for every peer.
• generate: if you want to generate a certificate for the target requested by the client.

Reference a certificate that includes its private key that you have already uploaded to SPS. For details, see Certificates stored on SPS.

Configures the encryption used in the sessions.

• disabled: Use unencrypted connection between the HTTP client and server.

  "transport_security": {
      "selection": "disabled"
  },

• client-only: Enables half-sided TLS encryption. Require HTTPS on client side, and HTTP on server side.

  "transport_security": {
      "selection": "client-only"
  }

• client-server: Enables end-to-end TLS-encryption. To allow unencrypted HTTP requests in addition to HTTPS requests, set allow_non_encrypted to true.

  "transport_security": {
      "selection": "client-server",
      "allow_non_encrypted": true
      "server_certificate_check": {}
  }

By default, SPS accepts any certificate shown by the server.

"server_certificate_check": {
    "enabled": false
},

To verify the certificate of the destination server, configure and reference a Trusted CA list.

"server_certificate_check": {
    "enabled": true,
    "trusted_ca": "9106862955a844051d7bf6"
},

To verify the certificate of the destination server, set to true. In this case, you will also have to reference a trusted_ca.

Reference a Trusted CA list.

Selects the certificate to show to the peers. You have the following options:

• Use the same certificate for each connection:

  Select this option if you want to use the same certificate for each connection. Note that you must reference a certificate that includes its private key that you have already uploaded to SPS. For details, see Certificates stored on SPS.

  "host_certification_method": {
      "selection": "fix",
      "x509_identity": "893b7eb7-8c6f-403a-ba3a-1d09dc4b4c7a"
  }

• Generate a certificate for the target requested by the client:

  Select this option if you want to generate a certificate for the target requested by the client. Note that you must reference a Signing CA that you have already configured on SPS. For details, see Signing CA policies.

  "host_certification_method": {
      "selection": "generate",
      "signing_ca": "1904188625a843f11d30a5"
  },

Possible values:

• fix: if you want to use the same certificate for every peer.
• generate: if you want to generate a certificate for the target requested by the client.

Reference a certificate that includes its private key that you have already uploaded to SPS. For details, see Certificates stored on SPS.

The usergroup (local or LDAP) who can authorize or audit the connection.

Local usergroups can be added or modified at the /api/configuration/aaa/local_database/groups/ endpoint.

Defines the permissions of the authorizer usergroup. Possible values are:

• audit

  The usergroup with the audit permission can monitor ongoing connections, and download the audit trails of a closed and indexed connection.

• authorize

  The usergroup with the authorize permission can authorize connection requests.

• audit_and_authorize

  The usergroup with the audit_and_authorize permission can authorize connection requests, monitor connections, and download the audit trail of closed and indexed connections.

The usergroup (local or LDAP) that is subject to the access control policy.

Local usergroups can be added or modified at the /api/configuration/aaa/local_database/groups/ endpoint.