SPS stores the host keys and X.509 certificates of the trusted servers. When a client tries to connect to a server, SPS verifies the host key or the certificate of the server, and allows connections only to the servers that have their keys available on SPS (unless the SSH Connection Policy is configured differently).
GET https://<IP-address-of-SPS>/api/ssh-host-keys
Cookie name | Description | Required | Values |
---|---|---|---|
session_id | Contains the authentication token of the user | Required |
The value of the session ID cookie received from the REST server in the authentication response, for example, a1f71d030e657634730b9e887cb59a5e56162860. For details on authentication, see Authenticate to the SPS REST API. Note that this session ID refers to the connection between the REST client and the SPS REST API. It is not related to the sessions that SPS records (and which also have a session ID, but in a different format). |
The following command lists the SSH host keys and certificates of the servers that the users can connect to using SSH.
curl --cookie cookies https://<IP-address-of-SPS>/api/ssh-host-keys/
The following command retrieves the properties of a specific key.
curl --cookie cookies https://<IP-address-of-SPS>/api/ssh-host-keys/<object-id>
The following is a sample response received when listing SSH host keys and certificates from the https:<IP-address-of-SPS>/api/ssh-host-keys/ endpoint.
For details of the meta object, see Message format.
The key of these objects is in the following format: <type-of-the-key>-<host-address>:<host-port>.
{ "meta": { "href": "/api/ssh-host-keys", "parent": "/api" }, "items": [ { "key": "ssh-dss-10.110.0.1:22", "meta": {"href": "/api/ssh-host-keys/ssh-dss-10.110.0.1:22"} }, { "key": "ssh-dss-10.110.0.2:2222", "meta": {"href": "/api/ssh-host-keys/ssh-dss-10.110.0.2:2222"} }, { "key": "ssh-rsa-10.110.0.1:22", "meta": {"href": "/api/ssh-host-keys/ssh-rsa-10.110.0.1:22"} }, { "key": "x509v3-sign-rsa-d00::2222:dead:2222", "meta": {"href": "/api/ssh-host-keys/x509v3-sign-rsa-d00::2222:dead:2222"} } ] }
When retrieving the endpoint of a specific host key, the response is the following.
{ "key": "ssh-rsa-10.10.100.1:22", "meta": { "href": "/api/ssh-host-keys/ssh-rsa-10.10.100.1:22", "parent": "/api/ssh-host-keys" }, "ssh-rsa-10.10.100.1:22": { "address": "10.10.100.1", "port": 22, "type": { "selection": "ssh-rsa", "value": "AAAAB3NzaC1yc2EAAAABIwAAAQEAxrtNxBZieXhBI2gJoAdsjKNq...==" } } }
The following table lists the typical status and error codes for this request. For a complete list of error codes, see Application level error codes.
Code | Description | Notes |
---|---|---|
201 | Created | The new resource was successfully created. |
400 | InvalidQuery | The requested filter or its value is invalid. |
401 | Unauthenticated | The requested resource cannot be retrieved because the client is not authenticated and the resource requires authorization to access it. The details section contains the path that was attempted to be accessed, but could not be retrieved. |
403 | Unauthorized | The requested resource cannot be retrieved because the client is not authorized to access it. The details section contains the path that was attempted to be accessed, but could not be retrieved. |
404 | NotFound | The requested object does not exist. |
To list only specific host keys, you can use the following filters.
List every host key and certificate:
GET https://<IP-address-of-SPS>/api/ssh-host-keys
List host keys of a specific type:
GET https://<IP-address-of-SPS>/api/ssh-host-keys?type=<type-to-list>
Possible values: ssh-rsa, ssh-dss, x509v3-sign-rsa, x509v3-sign-dss. For example:
GET https://<IP-address-of-SPS>/api/ssh-host-keys?type=ssh-rsa
List host keys for a specific port number:
GET https://<IP-address-of-SPS>/api/ssh-host-keys?port=<port-number-to-list>
List host keys for a specific host address (IPv4 or IPv6):
GET https://<IP-address-of-SPS>/api/ssh-host-keys?address=<host-address>
For a complex filter, separate the parameters with an ampersand (&) character, for example:
GET https://<IP-address-of-SPS>/api/ssh-host-keys?port=<port-number-to-list>&type=<type-to-list>
The response to such requests is a JSON object, where the items list includes the IDs of the selected host keys (or an empty list). For example, filtering for ssh-dss keys could return a similar list:
{ "meta": { "href": "/api/ssh-host-keys", "parent": "/api" }, "items": [ { "key": "ssh-dss-10.110.0.1:22", "meta": {"href": "/api/ssh-host-keys/ssh-dss-10.110.0.1:22"} }, { "key": "ssh-dss-10.110.0.2:2222", "meta": {"href": "/api/ssh-host-keys/ssh-dss-10.110.0.2:2222"} } ] }
To upload a new host key or certificate, you have to POST the host key and other data as a JSON object to the https://<IP-address-of-SPS>/api/ssh-host-keys endpoint. For details, see Create a new object. The body of the POST request must contain a JSON object with the parameters listed in Element . If the POST request is successful, the response includes an ID for the host key in the following format: <type-of-the-key>-<host-address>:<host-port>. For example:
{ "address": "10.110.0.1", "port": 22, "type": { "selection": "ssh-rsa", "value": "AAAAB3NzaC1yc2EAAAAD...zvMwgc==" } }
Note that for IPv6 addresses, SPS will automatically convert the address to its canonical format.
To delete a host key or certificate, you have to DELETE https://<IP-address-of-SPS>/api/ssh-host-keys/<ID-of-the-host-key> endpoint. For details, see Delete an object. If the DELETE request is successful, the response includes only the meta object, for example:
{ "meta": { "href": "/api/ssh-host-keys/ssh-rsa-10.10.20.35:22", "parent": "/api/ssh-host-keys" } }
You must commit your changes to actually delete the object from SPS.
List of endpoints for configuring the policies, options and connection rules of Telnet connections.
GET https://<IP-address-of-SPS>/api/configuration/telnet
Cookie name | Description | Required | Values |
---|---|---|---|
session_id | Contains the authentication token of the user | Required |
The value of the session ID cookie received from the REST server in the authentication response, for example, a1f71d030e657634730b9e887cb59a5e56162860. For details on authentication, see Authenticate to the SPS REST API. Note that this session ID refers to the connection between the REST client and the SPS REST API. It is not related to the sessions that SPS records (and which also have a session ID, but in a different format). |
The following command lists the available settings for configuring for Telnet connections.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/telnet
The following is a sample response received when listing the configuration settings.
For details of the meta object, see Message format.
{ "items": [ { "key": "authentication_policies", "meta": { "href": "/api/configuration/telnet/authentication_policies" } }, { "key": "channel_policies", "meta": { "href": "/api/configuration/telnet/channel_policies" } }, { "key": "connections", "meta": { "href": "/api/configuration/telnet/connections" } }, { "key": "options", "meta": { "href": "/api/configuration/telnet/options" } }, { "key": "pattern_sets", "meta": { "href": "/api/configuration/telnet/pattern_sets" } } ], "meta": { "first": "/api/configuration/aaa", "href": "/api/configuration/telnet", "last": "/api/configuration/x509", "next": "/api/configuration/troubleshooting", "parent": "/api/configuration", "previous": "/api/configuration/ssh", "remaining_seconds": 600, "transaction": "/api/transaction" } }
Item | Description |
---|---|
connections | List of Telnet connection policies. |
channel_policies | List of available Telnet channel types. |
authentication_policies | List of the configured authentication methods that can be used in a connection. |
pattern_sets | List of the default and custom channel policies. |
options | List of global Telnet options that affect all connections. |
The following table lists the typical status and error codes for this request. For a complete list of error codes, see Application level error codes.
Code | Description | Notes |
---|---|---|
401 | Unauthenticated | The requested resource cannot be retrieved because the client is not authenticated and the resource requires authorization to access it. The details section contains the path that was attempted to be accessed, but could not be retrieved. |
403 | Unauthorized | The requested resource cannot be retrieved because the client is not authorized to access it. The details section contains the path that was attempted to be accessed, but could not be retrieved. |
404 | NotFound | The requested object does not exist. |
Connection policies determine if a server can be accessed from a particular client. Connection policies reference other resources (policies, usergroups, keys) that must be configured and available before creating a connection policy.
GET https://<IP-address-of-SPS>/api/configuration/telnet/connections/
Cookie name | Description | Required | Values |
---|---|---|---|
session_id | Contains the authentication token of the user | Required |
The value of the session ID cookie received from the REST server in the authentication response, for example, a1f71d030e657634730b9e887cb59a5e56162860. For details on authentication, see Authenticate to the SPS REST API. Note that this session ID refers to the connection between the REST client and the SPS REST API. It is not related to the sessions that SPS records (and which also have a session ID, but in a different format). |
The following command lists Telnet connection policies.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/telnet/connections/
The following command retrieves the properties of a specific policy.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/telnet/connections/<connection-key>
The following is a sample response received when listing Telnet connection policies.
For details of the meta object, see Message format.
{ "items": [ { "key": "8348340645707e2575e3c6", "meta": { "href": "/api/configuration/telnet/connections/8348340645707e2575e3c6" } } ], "meta": { "first": "/api/configuration/telnet/channel_policies", "href": "/api/configuration/telnet/connections", "last": "/api/configuration/telnet/options", "next": "/api/configuration/telnet/options", "order": "/api/configuration/telnet/connections/@order", "parent": "/api/configuration/telnet", "previous": "/api/configuration/telnet/channel_policies", "remaining_seconds": 600, "transaction": "/api/transaction" } }
When retrieving the endpoint of a specific Telnet Connection Policy, the response is the following.
{ "body": { "access_control": [], "active": true, "channel_database_cleanup": { "enabled": false }, "client_side_transport_security": { "selection": "disabled" }, "indexing": { "enabled": true, "policy": { "key": "-50000", "meta": { "href": "/api/configuration/policies/indexing/-50000" } }, "priority": 3 }, "log_audit_trail_downloads": true, "name": "demo_telnet", "network": { "clients": [ "0.0.0.0/0" ], "ports": [ 23 ], "targets": [ "10.30.255.0/24" ] }, "override_log_level": { "enabled": true, "log_level": 3 }, "policies": { "aa_plugin": null, "analytics_policy": { "key": "20509709385cd578654cdab", "meta": { "href": "/api/configuration/policies/analytics/20509709385cd578654cdab" } }, "archive_cleanup_policy": null, "audit_policy": { "key": "78101850949e47437dd91d", "meta": { "href": "/api/configuration/policies/audit_policies/78101850949e47437dd91d" } }, "authentication_policy": { "key": "-400", "meta": { "href": "/api/configuration/telnet#authentication_policies/-400" } }, "backup_policy": null, "channel_policy": { "key": "-30200", "meta": { "href": "/api/configuration/telnet/channel_policies/-30200" } }, "credential_store": null, "ldap_server": null, "settings": { "key": "-302", "meta": { "href": "/api/configuration/telnet#settings_policies/-302" } }, "usermapping_policy": null }, "rate_limit": { "enabled": false }, "server_address": { "custom_dns": { "enabled": false }, "selection": "original" }, "server_side_transport_security": { "selection": "disabled" }, "source_address": { "selection": "box_address" }, "web_gateway_authentication": { "enabled": false } }, "key": "18762920615d68fa3d858d0", "meta": { "first": "/api/configuration/telnet/connections/18762920615d68fa3d858d0", "href": "/api/configuration/telnet/connections/18762920615d68fa3d858d0", "last": "/api/configuration/telnet/connections/18762920615d68fa3d858d0", "next": null, "parent": "/api/configuration/telnet/connections", "previous": null, "remaining_seconds": 600, "transaction": "/api/transaction" } }
Element | Type | Description | ||
---|---|---|---|---|
key | string | Top level element, contains the ID of the connection policy. | ||
body | Top level element (string) | The elements of the connection policy. | ||
access_control | Top level list |
Collection of access policies. Access policies define who can authorize and audit a connection. | ||
active | boolean | Set to false to suspend the connection policy. Connection settings are preserved. | ||
channel_database_cleanup | Top level item | Configures cleanup of the connection metadata on the connection policy's level. | ||
client_side_transport_security | Top level item |
Defines the Transport Layer Security (TLS) settings for the connection between SPS and the client. For example: "client_side_transport_security": { "selection": "disabled" }, | ||
days | int |
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 Telnet protocol are available at the api/configuration/telnet/options endpoint. | ||
enabled | boolean | Set to true to enable periodical cleanup of the connection metadata. | ||
indexing | Top level item | Configures indexing for the connection policy. | ||
enabled | boolean | Set to true to enable indexing the connections. | ||
policy | string |
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). | ||
priority | int |
Specifies the indexing priority for the connection. Possible values are:
| ||
log_audit_trail_downloads | boolean |
Set to true to log audit trail downloads. | ||
name | string | The name of the connection policy. | ||
network | ||||
clients | list, string | List of client ("from") IP addresses. | ||
ports | list, integers | List of target ports. | ||
targets | list, string | List of target IP addresses. | ||
override_log_level | Top level item |
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.
| ||
policies | Top level item | List of policies referenced by the connection policy. | ||
aa_plugin | string |
References the identifier of the AA plug-in. You can configure AA plug-ins at the /api/configuration/plugins/aa/ endpoint. To modify or add an AA plug-in, use the value of the returned key as the value of the aa_plugin element, and remove any child elements (including the key). | ||
analytics_policy | string |
References the identifier of the analytics policy. You can configure analytics policies at the /api/configuration/analytics/ endpoint. To add or modify an analytics policy, use the value of the returned key as the value of the analytics element, and remove any child elements (including the key). | ||
archive_cleanup_policy | string |
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). | ||
audit_policy | string |
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). | ||
authentication_policy | string |
Cannot be null. References the identifier of the authentication policy. Note that currently you cannot create or modify Telnet Authentication Policies using the REST API. Use the web UI instead. 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). | ||
backup_policy | string |
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). | ||
channel_policy | string |
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 Telnet channel policies at the /api/configuration/telnet/channel_policies/ endpoint. | ||
credential_store | string |
References the identifier of the credential store. You can configure credential stores at the /api/configuration/policies/credentialstores/ endpoint. To modify or add a credential store, use the value of the returned key as the value of the credential_store element, and remove any child elements (including the key). | ||
ldap_server | string |
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). | ||
settings | string |
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). | ||
usermapping_policy | string |
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). | ||
rate_limit | Top level element | Connection rate limit. | ||
enabled | boolean | Set to true to provide a connection rate limit. | ||
value | int | The number of connections (per minute) that are allowed in the connection policy. | ||
server_address | Top level item | Defines the address where the clients connect to. | ||
server_side_transport_security | Top level item |
Defines the Transport Layer Security (TLS) settings for the connection between SPS and the server. For example: "server_side_transport_security": { "selection": "disabled" }, | ||
source_address | Top level element | Allows you to configure Source Network Address Translation (SNAT) on the server side of SPS. SNAT determines the IP address SPS uses in the server-side connection. The target server will see the connection coming from this address. | ||
selection | string |
Configures Source Network Address Translation. Possible values are:
| ||
address | string |
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. | ||
web_gateway_authentication | Top level item | When gateway authentication is required for a connection, the user must authenticate on SPS as well. This additional authentication can be performed out-of-band on the SPS web interface for every protocol. | ||
enabled | boolean | Set to true to enable additional gateway authentication on the SPS web interface. | ||
groups | list, string |
By default, any user can perform gateway authentication for the connections. You can restrict authentication to members of specific usergroups. Define the usergroups at the /api/configuration/aaa/local_database/groups/ endpoint, and list the name of each group here. | ||
require_same_ip | boolean | Set to true to only accept web gateway authentication from the same host that initiated the connection. |
Elements of access_control | Type | Description | |
---|---|---|---|
authorizer | string |
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. | |
permission | string |
Defines the permissions of the authorizer usergroup. Possible values are:
| |
require_different_ip | boolean | Set to true to require the authorizing user and its subject to have different IP addresses. | |
require_different_username | boolean | Set to true to require the authorizing user and its subject to have different usernames. | |
subject | Top level item | Defines the subjects of the access control policy. | |
group | string |
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. | |
selection | string |
Possible values:
|
Elements of client_side_transport_security | Type | Description | |
---|---|---|---|
peer_certificate_check | Top level item |
Sets how SPS authenticates the peers. To permit connections from peers without requesting a certificate, set "enabled": false, for example: "peer_certificate_check": { "enabled": false } To validate the certificate of the peer, set "enabled": true, and reference a trusted certificate authority list, for example: "peer_certificate_check": { "enabled": true, "trusted_ca": "cfc815e5-dadb-4eb9-a628-12ae0c12d358" } | |
selection | string |
Sets the encryption settings used between SPS and the client. When the connection is encrypted, SPS has to show a certificate to the client, so you must configure the sps_certificate option as well. The possible values of selection are:
| |
sps_certificate | JSON object |
Sets the certificate that SPS shows to the peer when the communication is encrypted. SPS can either use the same certificate for every session, or generate a separate certificate fpr each session.
|
Elements of server_address | Type | Description | ||
---|---|---|---|---|
custom_dns | string |
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.
| ||
selection | string |
Configures the address where the clients connect to. Possible values are:
| ||
network | string |
Must be used if selection is set to nat. The target address in IP/prefix format. Example: "10.20.30.40/24". | ||
address | string |
Must be used if selection is set to fix. The IP address of the target server. | ||
port | int |
Must be used if selection is set to fix. The port of the target server. | ||
domains | Top level list |
Must be used if selection is set to inband. | ||
domain | Top level item | Lists the address ranges that are included in the connection policy. | ||
selection | string |
Specifies if the target address range is provided as a domain or as an IP range. Possible values are:
| ||
value | string |
The address range of the target server(s). Use the selection element to specify if the address is an IP range, or a domain. | ||
port | int | The port of the targer server(s). | ||
exception_domains | Top level list |
Can only be used if selection is set to inband. Lists the address ranges that are excluded from the connection policy. | ||
domain | Top level item | Contains the excluded address range. | ||
selection | string |
Specifies if the excluded address(es) are provided as a domain or as an IP range. Possible values are:
| ||
value | string |
The excluded address(es). Use the selection element to specify if the address is an IP range, or a domain. | ||
port | int | The excluded port. | ||
dns_server | string |
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. | ||
dns_suffixes | list, string |
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. |
Elements of server_side_transport_security | Type | Description | |
---|---|---|---|
peer_certificate_check | Top level item |
Sets how SPS authenticates the peers. To permit connections from peers without requesting a certificate, set "enabled": false, for example: "peer_certificate_check": { "enabled": false } To validate the certificate of the peer, set "enabled": true, and reference a trusted certificate authority list, for example: "peer_certificate_check": { "enabled": true, "trusted_ca": "cfc815e5-dadb-4eb9-a628-12ae0c12d358" } | |
selection | string |
Sets the encryption settings used between SPS and the server. If SPS has to show a certificate to the peer, so you must configure the sps_certificate option as well. The possible values of selection are:
| |
sps_certificate | JSON object |
Sets the certificate that SPS shows to the peer when the communication is encrypted. SPS can either use the same certificate for every session, or generate a separate certificate fpr each session.
|
The following table lists the typical status and error codes for this request. For a complete list of error codes, see Application level error codes.
Code | Description | Notes |
---|---|---|
201 | Created | The new resource was successfully created. |
400 | InvalidQuery | The requested filter or its value is invalid. |
401 | Unauthenticated | The requested resource cannot be retrieved because the client is not authenticated and the resource requires authorization to access it. The details section contains the path that was attempted to be accessed, but could not be retrieved. |
403 | Unauthorized | The requested resource cannot be retrieved because the client is not authorized to access it. The details section contains the path that was attempted to be accessed, but could not be retrieved. |
404 | NotFound | The requested object does not exist. |
To add a Telnet connection policy, you have to:
For details, see Open a transaction.
POST the JSON object to the https://<IP-address-of-SPS>/api/configuration/telnet/connections/ endpoint. You can find a detailed description of the available parameters listed in Element .
If the POST request is successful, the response includes the key of the new Telnet connection policy. For example:
{ "key": "a99be49b-b0a2-4cf9-b70d-fea1f9ea188f", "meta": { "href": "/api/configuration/telnet/connections/a99be49b-b0a2-4cf9-b70d-fea1f9ea188f", "parent": "/api/configuration/telnet/connections", "transaction": "/api/transaction" } }
For details, see Commit a transaction.
To modify a Telnet connection policy, you have to:
For details, see Open a transaction.
PUT the modified JSON object to the https://<IP-address-of-SPS>/api/configuration/telnet/connections/<key-of-the-object> endpoint. You can find a detailed description of the available parameters listed in Element .
For details, see Commit a transaction.
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center