List of endpoints for configuring the policies, options and connection rules of MSSQL connections.
GET https://<IP-address-of-SPS>/api/configuration/mssql
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 MSSQL connections.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/mssql
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/mssql/authentication_policies" } }, { "key": "channel_policies", "meta": { "href": "/api/configuration/mssql/channel_policies" } }, { "key": "connections", "meta": { "href": "/api/configuration/mssql/connections" } }, { "key": "options", "meta": { "href": "/api/configuration/mssql/options" } }, { "key": "settings_policies", "meta": { "href": "/api/configuration/mssql/settings_policies" } } ], "meta": { "first": "/api/configuration/aaa", "href": "/api/configuration/mssql", "last": "/api/configuration/x509", "next": "/api/configuration/network", "parent": "/api/configuration", "previous": "/api/configuration/management", "remaining_seconds": 600, "transaction": "/api/transaction" } }
Item | Description |
---|---|
connections | List of connection policies. |
authentication_policies | List of the default and custom authentication policies. |
channel_policies | List of the default and custom channel policies. |
options | List of global MSSQL options that affect all connections. |
settings_policies | List of protocol-level settings (idle and session timeout). You can create multiple variations, and choose the appropriate one for each connection policy. |
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/mssql/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 MSSQL connection policies.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/mssql/connections/
The following command retrieves the properties of a specific policy.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/mssql/connections/<connection-key>
The following is a sample response received when listing MSSQL connection policies.
For details of the meta object, see Message format.
{ "items": [ { "key": "19443158785dee0621437ad", "meta": { "href": "/api/configuration/mssql/connections/19443158785dee0621437ad" } } ], "meta": { "first": "/api/configuration/mssql/channel_policies", "href": "/api/configuration/mssql/connections", "last": "/api/configuration/mssql/options", "next": "/api/configuration/mssql/options", "order": "/api/configuration/mssql/connections/@order", "parent": "/api/configuration/mssql", "previous": "/api/configuration/mssql/channel_policies", "remaining_seconds": 600, "transaction": "/api/transaction" } }
When retrieving the endpoint of a specific MSSQL Connection Policy, the response is the following.
{ "body": { "access_control": [], "active": true, "channel_database_cleanup": { "enabled": false }, "indexing": { "enabled": true, "policy": { "key": "-50000", "meta": { "href": "/api/configuration/policies/indexing/-50000" } }, "priority": 3 }, "log_audit_trail_downloads": true, "name": "demo_mssql", "network": { "clients": [ "0.0.0.0/0" ], "ports": [ 1433 ], "targets": [ "192.168.1.1/24" ] }, "override_log_level": { "enabled": false }, "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": "-30700201", "meta": { "href": "/api/configuration/mssql/authentication_policies/-30700201" } }, "backup_policy": null, "channel_policy": { "key": "-30700102", "meta": { "href": "/api/configuration/mssql/channel_policies/-30700102" } }, "credential_store": null, "ldap_server": null, "settings": { "key": "-30700301", "meta": { "href": "/api/configuration/mssql/settings_policies/-30700301" } }, "usermapping_policy": null }, "rate_limit": { "enabled": false }, "server_address": { "custom_dns": { "enabled": false }, "selection": "original" }, "source_address": { "selection": "box_address" }, "transport_security": { "selection": "disabled" }, "web_gateway_authentication": { "enabled": false } }, "key": "19443158785dee0621437ad", "meta": { "first": "/api/configuration/mssql/connections/19443158785dee0621437ad", "href": "/api/configuration/mssql/connections/19443158785dee0621437ad", "last": "/api/configuration/mssql/connections/19443158785dee0621437ad", "next": null, "parent": "/api/configuration/mssql/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. | ||
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 MSSQL protocol are available at the api/configuration/mssql/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 MSSQL 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 MSSQL channel policies at the /api/configuration/mssql/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. | ||
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. | ||
transport_security | Top level element |
Configures the encryption used in the sessions. | ||
certificate | JSON object |
Selects the certificate to show to the peers. You have the following options:
| ||
selection | disabled | tls |
Configures the encryption used in the sessions.
| ||
server_certificate_check | JSON object |
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" }, | ||
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 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. |
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 MSSQL connection policy, you have to:
For details, see Open a transaction.
POST the JSON object to the https://<IP-address-of-SPS>/api/configuration/mssql/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 MSSQL connection policy. For example:
{ "key": "a99be49b-b0a2-4cf9-b70d-fea1f9ea188f", "meta": { "href": "/api/configuration/mssql/connections/a99be49b-b0a2-4cf9-b70d-fea1f9ea188f", "parent": "/api/configuration/mssql/connections", "transaction": "/api/transaction" } }
For details, see Commit a transaction.
To modify a MSSQL 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/mssql/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.
The available MSSQL channel types and their functionalities are described below. For details on configuring channel policies, see Channel policy.
Channel | Special options | Description |
---|---|---|
mssql | Yes |
mssql: Enables access to the MSSQL server. This channel must be enabled for MSSQL to work. Channel-specific actions:
For example: "actions": { "audit": true, "four_eyes": true, "content_policy": { "key": "433849548566ab327522e6" "meta": { "href": "/api/configuration/policies/content_policies/44287216854f482e7f2b24" } }, } |
Lists the configured authentication methods that can be used in a connection. Each connection policy uses an authentication policy to determine how the client can authenticate on the SPS gateway.
GET https://<IP-address-of-SPS>/api/configuration/mssql/authentication_policies
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 MSSQL authentication policies.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/mssql/authentication_policies
The following command retrieves the properties of a specific policy.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/mssql/authentication_policies<object-id>
The following is a sample response received when listing MSSQL authentication policies.
For details of the meta object, see Message format.
{ "items": [ { "key": "-200", "meta": { "href": "/api/configuration/mssql/authentication_policies/-200" } }, { "key": "-304002001", "meta": { "href": "/api/configuration/mssql/authentication_policies/-304002001" } } ], "meta": { "first": "/api/configuration/mssql/authentication_policies", "href": "/api/configuration/mssql/authentication_policies", "last": "/api/configuration/mssql/settings_policies", "next": "/api/configuration/mssql/channel_policies", "parent": "/api/configuration/mssql", "previous": null, "transaction": "/api/transaction" } }
When retrieving the endpoint of a specific policy, the response is the following.
{ "body": { "backend": { "selection": "ldap" }, "name": "mssql_auth_policy_with_ldap" } }
Element | Type | Description | ||
---|---|---|---|---|
key | string | Top level element, contains the ID of the policy. | ||
body | Top level element | Contains the elements of the policy. | ||
name | string | The name of the object. This name is also displayed on the SPS web interface. It cannot contain whitespace. | ||
backend | Top level item | Client-side gateway authentication settings. The value of selection defines which authentication method is used. | ||
selection | string |
Defines the authentication method for client-side gateway authentication. Possible values are:
| ||
servers | Top level list |
Only if selection is set to radius Defines the properties of the RADIUS servers used for client-side authentication. A valid list item consists of the address, port and shared_secret elements. | ||
authentication_protocol | Top level item |
Only if selection is set to radius RADIUS setting. Set to pap to use the Password Authentication Protocol. To use the Challenge-Handshake Authentication Protocol, set it to chap. | ||
user_database | string |
Only if selection is set to local References the key of the local user database. You can configure local user databases at the /api/configuration/policies/user_databases/ endpoint. To modify or add a local user database, use the value of the returned key as the value of the user_database element, and remove any child elements (including the key). | ||
timeout | integer (seconds) | Specify the time remaining until a successful gateway authentication times out. | ||
keepalive | boolean | Set to true to avoid interruptions for active HTTP sessions. Active HTTP sessions can extend the gateway authentication beyond the configured timeout. |
Elements of servers | Type | Description | |
---|---|---|---|
address | Top level element | Defines the address of a RADIUS server. | |
selection | string |
Required child of the address element. Possible values are:
| |
value | string | The IP or the FQDN address of the RADIUS server. | |
port | int | The port number of the RADIUS server. | |
shared_secret | string |
References the key of the shared secret for the RADIUS server. You can configure shared secrets at the /api/configuration/passwords/ endpoint. To modify or add a shared secret, use the value of the returned key as the value of the shared_secret element, and remove any child elements (including the key). Alternatively, you can include the new password as plain text. "shared_secret": { "plain": "<new-password>" } |
Querying base authentication policy without gateway authentication:
{ "key": "-304002001", "body": { "name": "base", "backend": { "selection": "none" } } }
Querying authentication policy with LDAP backend:
{ "key": "mssql-auth-pol-2", "body": { "name": "mssql_ldap", "backend": { "selection": "ldap", "timeout": 3600, "keepalive": true } } }
Querying authentication policy with local backend:
{ "key": "mssql-auth-pol-3", "body": { "name": "mssql_local", "backend": { "selection": "local", "user_database": { "key": "local-user-database-1", "meta": { "href": "/api/configuration/policies/user_databases/local-user-database-1" } }, "timeout": 3600, "keepalive": true } } }
Querying authentication policy with RADIUS backend:
{ "key": "mssql-auth-pol-4", "body": { "name": "mssql_radius", "backend": { "selection": "radius", "servers": [ { "address": { "selection": "ip", "value": "1.2.3.4" }, "port": 1812, "shared_secret": { "key": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", "meta": { "href": "/api/configuration/passwords#XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" } } } ], "authentication_protocol": "pap", "timeout": 3600, "keepalive": true } } }
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 MSSQL authentication policy, you have to:
For details, see Open a transaction.
POST the JSON object to the https://<IP-address-of-SPS>/api/configuration/mssql/authentication_policies/ endpoint. You can find a detailed description of the available parameters listed in MSSQL authentication policies.
If the POST request is successful, the response includes the key of the new policy. For example:
{ "key": "6f924f39-e4c9-4b0f-8018-8842e2115ebd", "meta": { "href": "/api/configuration/mssql/authentication_policies/6f924f39-e4c9-4b0f-8018-8842e2115ebd", "parent": "/api/configuration/mssql/authentication_policies", "transaction": "/api/transaction" } }
For details, see Commit a transaction.
To modify a MSSQL authentication policy, you have to:
For details, see Open a transaction.
PUT the modified JSON object to the https://<IP-address-of-SPS>/api/configuration/mssql/authentication_policies/<key-of-the-object> endpoint. You can find a detailed description of the available parameters listed in MSSQL authentication policies.
For details, see Commit a transaction.
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center