List of options that affect all MSSQL connections.
URL
GET https://<IP-address-of-SPS>/api/configuration/mssql/options
Cookies
| 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 more information on authentication, see Authenticate to the SPS REST API.
NOTE: 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 MSSQL options.
curl --cookie cookies.txt https://<IP-address-of-SPS>/api/configuration/mssql/options
Response
The following is a sample response received when listing global MSSQL options.
For more information on the meta object, see Message format.
{
"body": {
"channel_database_cleanup": {
"enabled": false
},
"service": {
"enabled": false
}
}
"key": "options",
"meta": {
"first": "/api/configuration/mssql/channel_policies",
"href": "/api/configuration/mssql/options",
"last": "/api/configuration/mssql/options",
"next": null,
"parent": "/api/configuration/mssql",
"previous": "/api/configuration/mssql/channel_policies",
"transaction": "/api/transaction"
}
}
| key |
|
Top level item |
Contains the ID of the endpoint. |
| body |
|
Top level item |
Contains the elements of the global MSSQL options. |
| |
channel_database_cleanup |
Top level item |
Contains settings for database cleanup. |
| |
service |
Top level item |
Global setting to enable MSSQL connections, and specify the logging detail. |
| days |
integer |
Applies only if enabled is set to true.
Global retention time for the metadata of MSSQL connections, in days. Must exceed the retention time of the archiving policy (or policies) used for MSSQL connections, and the connection-specific database cleanup times (if configured). |
|
enabled |
boolean |
To enable the global cleanup of MSSQL connection metadata, set enabled to true. |
| log_level |
integer |
Applies only if enabled is set to true.
Defines the logging detail of MSSQL connections. |
|
enabled |
boolean |
To enable MSSQL connections, set to true. |
Examples
Querying the full list of global MSSQL options:
{
"body": {
"channel_database_cleanup": {
"enabled": true,
"days": 365
},
"service": {
"enabled": true,
"log_level": 4
}
}
"key": "options",
"meta": {
"first": "/api/configuration/mssql/channel_policies",
"href": "/api/configuration/mssql/options",
"last": "/api/configuration/mssql/options",
"next": null,
"parent": "/api/configuration/mssql",
"previous": "/api/configuration/mssql/channel_policies",
"transaction": "/api/transaction"
}
}
Modify global MSSQL settings
To modify global MSSQL settings,
-
Open a transaction.
For more information, see Open a transaction.
-
Modify the JSON object of the global MSSQL settings endpoint.
PUT the modified JSON object to the https://<IP-address-of-SPS>/api/configuration/mssql/options endpoint.
You can find a detailed description of the available parameters listed in Element.
For more information about the elements of the channel_database_cleanup item, see Elements of channel_database_cleanup.
For more information about the elements of the service item, see Elements of service.
-
Commit your changes.
For more information, 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.
| 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 the SPS REST API attempted to access, but could not retrieve. |
| 403 |
Unauthorized |
The requested resource cannot be retrieved because the client is not authorized to access it. The details section contains the path that the SPS REST API attempted to access, but could not retrieve. |
| 404 |
NotFound |
The requested object does not exist. |
MSSQL settings policies define protocol-level settings for idle timeout. You can create multiple policies, and choose the appropriate one for each MSSQL connection.
URL
GET https://<IP-address-of-SPS>/api/configuration/mssql/settings_policies
Cookies
| 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 more information on authentication, see Authenticate to the SPS REST API.
NOTE: 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 MSSQL settings policies.
curl --cookie cookies.txt https://<IP-address-of-SPS>/api/configuration/mssql/settings_policies
The following command retrieves the properties of a specific policy.
curl --cookie cookies.txt https://<IP-address-of-SPS>/api/configuration/mssql/settings_policies/<policy-id>
Response
The following is a sample response received when listing MSSQL settings policies.
For more information on the meta object, see Message format.
{
"items": [
{
"key": "-3040010",
"meta": {
"href": "/api/configuration/mssql/settings_policies/-3040010"
}
}
],
"meta": {
"first": "/api/configuration/mssql/channel_policies",
"href": "/api/configuration/mssql/settings_policies",
"last": "/api/configuration/mssql/settings_policies",
"next": null,
"parent": "/api/configuration/mssql",
"previous": "/api/configuration/mssql/options",
"transaction": "/api/transaction"
}
}
When retrieving the endpoint of a specific policy, the response is the following.
{
"body": {
"client_tls_security_settings": {
"cipher_strength": {
"selection": "recommended"
},
"minimum_tls_version": "TLSv1_2"
},
"name": "default",
"server_tls_security_settings": {
"cipher_strength": {
"selection": "recommended"
},
"minimum_tls_version": "TLSv1_2"
},
"preconnect_channel_check": false,
"timeout": 300
},
"key": "-3040010",
"meta": {
"first": "/api/configuration/mssql/settings_policies/-3040010",
"href": "/api/configuration/mssql/settings_policies/-3040010",
"last": "/api/configuration/mssql/settings_policies/-3040010",
"next": null,
"parent": "/api/configuration/mssql/settings_policies",
"previous": null,
"transaction": "/api/transaction"
}
}
| key |
|
string |
Top level element, contains the ID of the policy. |
| body |
|
Top level element (string) |
The elements of the MSSQL settings policy. |
|
client_tls_security_settings |
JSON object |
Configures TLS security settings on the client side. |
|
name |
string |
Name of the MSSQL settings policy. Cannot contain whitespace. |
|
server_tls_security_settings |
JSON object |
Configures TLS security settings on the server side. |
|
timeout |
int |
Idle timeout, in seconds. Note that the SPS web UI displays the same value in seconds. |
| cipher_strength |
|
JSON object |
Specifies the cipher string OpenSSL will use. |
|
custom_cipher |
string |
The list of ciphers you want to permit SPS to use in the connection. For more details on customizing this list, check the 'openssl-ciphers' manual page on your SPS appliance. |
|
selection |
string |
Specifies the cipher string OpenSSL will use. The following settings options are possible:
-
recommended: this setting only uses ciphers with adequate security level.
-
custom: this setting allows you to specify the list of ciphers you want to permit SPS to use in the connection. This setting is only recommended to ensure compatibility with older systems. For more details on customizing this list, check the 'openssl-ciphers' manual page on your SPS appliance.
For example: ALL:!aNULL:@STRENGTH |
| minimum_tls_version |
|
string |
Specifies the minimal TLS version SPS will offer during negotiation. The following settings options are possible:
-
TLSv1_2: this setting only offers TLS version 1.2 during the negotiation. This is the recommended setting.
-
TLSv1_1: this setting offers TLS version 1.1 and later versions during the negotiation.
-
TLSv1_0: this setting offers TLS version 1.0 and later versions during the negotiation. |
Add MSSQL settings policies
To add a settings policy, you have to:
-
Open a transaction.
For more information, see Open a transaction.
-
Create the JSON object for the new policy.
POST the JSON object to the https://<IP-address-of-SPS>/api/configuration/mssql/settings_policies/ 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 policy. For example:
{
"key": "3848c708-2e1d-4463-b232-0c8c5875ff55",
"meta": {
"href": "/api/configuration/mssql/settings_policies/3848c708-2e1d-4463-b232-0c8c5875ff55",
"parent": "/api/configuration/mssql/settings_policies",
"transaction": "/api/transaction"
}
}
-
Commit your changes.
For more information, see Commit a transaction.
Modify MSSQL settings policies
To modify a settings policy, you have to:
-
Open a transaction.
For more information, see Open a transaction.
-
Modify the JSON object of the policy.
PUT the modified JSON object to the https://<IP-address-of-SPS>/api/configuration/mssql/settings_policies/<key-of-the-object> endpoint. You can find a detailed description of the available parameters listed in Element .
-
Commit your changes.
For more information, 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.
| 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. |
| 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. |
List of endpoints for configuring the policies, options and connection rules of RDP connections.
URL
GET https://<IP-address-of-SPS>/api/configuration/rdp
Cookies
| 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 more information on authentication, see Authenticate to the SPS REST API.
NOTE: 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 the available settings for configuring for RDP connections.
curl --cookie cookies.txt https://<IP-address-of-SPS>/api/configuration/rdp
Response
The following is a sample response received when listing the configuration settings.
For more information on the meta object, see Message format.
{
"items": [
{
"key": "channel_policies",
"meta": {
"href": "/api/configuration/rdp/channel_policies"
}
},
{
"key": "connections",
"meta": {
"href": "/api/configuration/rdp/connections"
}
},
{
"key": "domain_membership",
"meta": {
"href": "/api/configuration/rdp/domain_membership"
}
},
{
"key": "options",
"meta": {
"href": "/api/configuration/rdp/options"
}
},
{
"key": "settings_policies",
"meta": {
"href": "/api/configuration/rdp/settings_policies"
}
}
],
"meta": {
"first": "/api/configuration/aaa",
"href": "/api/configuration/rdp",
"last": "/api/configuration/x509",
"next": "/api/configuration/reporting",
"parent": "/api/configuration",
"previous": "/api/configuration/private_keys",
"transaction": "/api/transaction"
}
}
| channel_policies |
List of the default and custom channel policies. |
| connections |
List of connection policies. |
| domain_membership |
Domain membership configuration. Prerequisite for configuring Credential Security Service Provider / Network Layer Authentication. |
| options |
List of global RDP options that affect all connections. |
| settings_policies |
List of protocol-level settings (timeout, display, protocol version, and authentication). You can create multiple variations, and choose the appropriate one for each connection policy. |
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.
| 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. |
