The SPS users can perform authentication-related activities (gateway authentication, 4-eyes authorization). On this endpoint you can configure on which interfaces can the users access SPS, and optionally restrict the access to these interfaces.
GET https://<IP-address-of-SPS>/api/configuration/local_services/user_web
Header 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 configuration options.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/local_services/user_web
The following is a sample response received when listing the configuration options. For details of the meta object, see Introduction.
{ "body": { "access_restriction": { "allowed_from": [ "10.40.0.0/16" ], "enabled": true }, "bruteforce_protection": true, "listen": [ { "address": { "key": "nic1.interfaces.ff7574025754b3df1647001.addresses.1", "meta": { "href": "/api/configuration/network/nics/nic1#interfaces/ff7574025754b3df1647001/addresses/1" } }, "http_port": 80, "https_port": 443 } ] }, "key": "user_web", "meta": { "first": "/api/configuration/local_services/user_web", "href": "/api/configuration/local_services/user_web", "last": "/api/configuration/local_services/user_web", "next": "/api/configuration/local_services/indexer", "parent": "/api/configuration/local_services", "previous": null, "transaction": "/api/transaction" } }
Element | Type | Description | ||
---|---|---|---|---|
key | string | Top level element, contains the ID of the endpoint. | ||
body | Top level element (string) | Contains the configuration options of the SPS web interface. | ||
access_restriction |
JSON object |
Enables and configures limitations on the clients that can access the web interface, based on the IP address of the clients. | ||
allowed_from |
list |
The list of IP networks from where the administrators are permitted to access this management interface. To specify the IP addresses or networks, use the IPv4-Address/prefix format, for example, 10.40.0.0/16. | ||
enabled |
boolean |
Set it to true to restrict access to the specified client addresses. | ||
bruteforce_protection | boolean | Enables protection against brute-force attacks by denying access after failed login attempts for increasingly longer period. Enabled by default. | ||
listen | list | Selects the network interface, IP address, and port where the clients can access the web interface. | ||
address | JSON object |
A reference to a configured network interface and IP address where this local service accepts connections. For example, if querying the interface /api/configuration/network/nics/nic1#interfaces/ff7574025754b3df1647001/addresses/ returns the following response: { "body": { "interfaces": { "@order": [ "ff7574025754b3df1647001" ], "ff7574025754b3df1647001": { "addresses": { "1": "10.40.255.171/24", "@order": [ "1" ] }, "name": "default", "vlantag": 0 } }, "name": "eth0", "speed": "auto" }, "key": "nic1", "meta": { "first": "/api/configuration/network/nics/nic1", "href": "/api/configuration/network/nics/nic1", "last": "/api/configuration/network/nics/nic3", "next": "/api/configuration/network/nics/nic2", "parent": "/api/configuration/network/nics", "previous": null, "transaction": "/api/transaction" } } Then the listening address of the local service is the following. nic1.interfaces.ff7574025754b3df1647001.addresses.1 This is the format you have to use when configuring the address of the local service using REST: "address": "nic1.interfaces.ff7574025754b3df1647001.addresses.1" When querying a local services endpoint, the response will contain a reference to the IP address of the interface in the following format: "address": { "key": "nic1.interfaces.ff7574025754b3df1647001.addresses.1", "meta": { "href": "/api/configuration/network/nics/nic1#interfaces/ff7574025754b3df1647001/addresses/1" } }, | ||
http_port | integer | The port number where SPS accepts HTTP connections. Note that SPS automatically redirects connections from this port to the HTTPS port set in https_port. | ||
https_port | integer | The port number where SPS accepts HTTPS connections. |
The following table lists the typical status and error codes for this request. For a complete list of error codes, see Using the SPS REST API.
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. |
401 | AuthenticationFailure | Authenticating the user with the given credentials has failed. |
404 | NotFound | The requested object does not exist. |
Contains the endpoints for configuring date and time on SPS.
GET https://<IP-address-of-SPS>/api/configuration/datetime
Header 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 endpoints for configuring date and time settings on SPS.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/datetime
The following is a sample response received when listing the endpoints for date and time settings. For details of the meta object, see Introduction.
{ "items": [ { "key": "ntp_servers", "meta": { "href": "/api/configuration/datetime/ntp_servers" } }, { "key": "timezone", "meta": { "href": "/api/configuration/datetime/timezone" } } ], "meta": { "first": "/api/configuration/aaa", "href": "/api/configuration/datetime", "last": "/api/configuration/x509", "next": "/api/configuration/http", "parent": "/api/configuration", "previous": "/api/configuration/alerting", "transaction": "/api/transaction" } }
Element | Description |
---|---|
ntp_servers | NTP server addresses. |
timezone | Timezone settings. |
The following table lists the typical status and error codes for this request. For a complete list of error codes, see Using the SPS REST API.
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. |
401 | AuthenticationFailure | Authenticating the user with the given credentials has failed. |
404 | NotFound | The requested object does not exist. |
This endpoint contains NTP server addresses.
GET https://<IP-address-of-SPS>/api/configuration/datetime/ntp_servers
Header 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 NTP server addresses.
curl --cookie cookies https://<IP-address-of-SPS>/api/configuration/datetime/ntp_servers
The following is a sample response received when listing NTP server addresses. For details of the meta object, see Introduction.
{ "body": [ { "selection": "fqdn", "value": "pool.ntp.org" } ], "key": "ntp_servers", "meta": { "first": "/api/configuration/datetime/ntp_servers", "href": "/api/configuration/datetime/ntp_servers", "last": "/api/configuration/datetime/timezone", "next": "/api/configuration/datetime/timezone", "parent": "/api/configuration/datetime", "previous": null, "transaction": "/api/transaction" } }
Element | Type | Description | |
---|---|---|---|
key | string | Top level element, contains the ID of the endpoint. | |
body | Top level element (list) | Contains the list of NTP server addresses. | |
selection | string |
Defines the address type (IP or domain name). Possible values are:
| |
value | string | The address of the NTP server. |
To add an NTP server's address, you have to:
For details, see Open a transaction.
POST the JSON object to the https://<IP-address-of-SPS>/api/configuration/datetime/ntp_servers endpoint. You can find a detailed description of the available parameters listed in NTP servers.
For details, see Commit a transaction.
To modify an NTP server's address, you have to:
For details, see Open a transaction.
PUT the modified JSON object to the https://<IP-address-of-SPS>/api/configuration/datetime/ntp_servers endpoint. You can find a detailed description of the available parameters listed in NTP servers.
For details, see Commit a transaction.
The following table lists the typical status and error codes for this request. For a complete list of error codes, see Using the SPS REST API.
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. |
401 | AuthenticationFailure | Authenticating the user with the given credentials has failed. |
404 | NotFound | The requested object does not exist. |
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy