List of options that affect all Telnet connections.
URL
GET https://<IP-address-of-SPS>/api/configuration/telnet/options
Cookies
| 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). |
Sample request
The following command lists global Telnet options.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/telnet/options
Response
The following is a sample response received when listing global Telnet options.
For details of the meta object, see Message format.
{
"body": {
"audit": {
"cleanup": {
"enabled": false
},
"timestamping": {
"selection": "local",
"signing_interval": 30
}
},
"service": {
"enabled": true,
"log_level": 4
}
},
"key": "options",
"meta": {
"first": "/api/configuration/telnet/channel_policies",
"href": "/api/configuration/telnet/options",
"last": "/api/configuration/telnet/options",
"next": null,
"parent": "/api/configuration/telnet",
"previous": "/api/configuration/telnet/channel_policies",
"transaction": "/api/transaction"
}
}
| Element | Type | Description | ||
|---|---|---|---|---|
| key | Top level item | Contains the ID of the endpoint. | ||
| body | Top level item | Contains the elements of the global Telnet options. | ||
| audit | Top level item | Contains settings for timestamping and cleanup. | ||
| service | Top level item | Global setting to enable Telnet connections, and specify the logging detail. | ||
| enabled | boolean | Set to true to enable Telnet connections. | ||
| log_level | int | Defines the logging detail of Telnet connections. | ||
Examples:
Set SPS as the timestamping server:
{
"audit": {
"cleanup": {
"enabled": false
},
"timestamping": {
"selection": "local",
"signing_interval": 30
}
},
"service": {
"enabled": true,
"log_level": 4
}
}
Enable cleanup, and set it to occur every 10 days:
{
"audit": {
"cleanup": {
"channel_database_cleanup_days": 10,
"enabled": true
},
"timestamping": {
"selection": "local",
"signing_interval": 30
}
},
"service": {
"enabled": true,
"log_level": 4
}
}
Change timestamping to a remote server, without specifying a timestamping policy:
{
"audit": {
"cleanup": {
"channel_database_cleanup_days": 10,
"enabled": true
},
"timestamping": {
"oid": {
"enabled": false
},
"selection": "remote",
"server_url": "<url-of-timestamping-server>",
"signing_interval": 30
}
},
"service": {
"enabled": true,
"log_level": 4
}
}
Change timestamping to a remote server, and specify the 1.2.3 timestamping policy:
{
"audit": {
"cleanup": {
"channel_database_cleanup_days": 10,
"enabled": true
},
"timestamping": {
"oid": {
"enabled": true,
"policy_oid": "1.2.3"
},
"selection": "remote",
"server_url": "<url-of-timestamping-server>",
"signing_interval": 30
}
},
"service": {
"enabled": true,
"log_level": 4
}
}
Modify global Telnet settings
To modify global Telnet settings, you have to:
-
Open a transaction.
For details, see Open a transaction.
-
Modify the JSON object of the global Telnet settings endpoint.
PUT the modified JSON object to the https://<IP-address-of-SPS>/api/configuration/telnet/options endpoint. You can find a detailed description of the available parameters listed in Element . The elements of the audit item are described in Elements of audit.
-
Commit your changes.
For details, see Commit a transaction.
Status and error codes
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. |
| 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. |
| 401 | AuthenticationFailure | Authenticating the user with the given credentials has failed. |
| 404 | NotFound | The requested object does not exist. |