APIv2
actions
list
Lists the available action methods.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
dig
Run dig (a DNS tool) on the specified appliances with the provided arguments.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances |
args_str required | Command line arguments for the dig command (see dig man page) |
download_logs
Prepare the log files for downloading on the specified appliances from from_date to to_date as ISO datetime strings.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances. |
from_date | Date/time to include logs from, in UTC ISO format.Default is now minus 2 days. |
to_date | Date/time to include logs up to, in UTC ISO format. Default is now. |
json_output |
environment_backup_create
Create an environment backup. Backups are accessible via SFTP on database and backend appliances.
environment_backup_list
List the file names of the environment backups: the manually created backups via environment-backup-create, the automatically created backups at the configured backup time and the backups uploaded via SFTP to the database appliance (if applicable).
environment_backup_restore
Restore a backup of the internal database. The environment will be unavailable while this is in progress.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
filename required | The file name of the backup to restore (see environment-backup-list) |
password | Password to decrypt the environment backup. Leave empty if the file is not encrypted (encrypted backups have the '.enc' extension). |
ip_address_appliances
Retrieve appliance ip. Sends a command to retrieve the appliances network ip.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances. |
ldapsearch
Run ldapsearch on the specified appliances with the provided arguments.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances. |
args_str required | Command line arguments for the ldapsearch command (see ldapsearch man page) |
ping
Run ping on the specified appliances with the provided arguments.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances. |
args_str required | Command line arguments for the ping command (see ping man page) |
shutdown_appliances
Shutdown all appliances. Sends a shutdown instruction with 1 minute delay to allow services to stop.
sync_appliances_time
Time sync on all appliances. Sends a command to force time sync on all appliances.
tcpscan
Run nmap on the specified appliances to check tcp ports with the provided ip/host and port/range of ports.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances |
host required | Hostname or an ip address |
port required | Single port, ports separated by comma (eg: 80,81) or a range of ports (eg: 80-85) |
traceroute
Run traceroute on the specified appliances with the provided arguments.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances. |
args_str required | Command line arguments for the traceroute command (see traceroute man page) |
udpscan
Run nmap on the specified appliances to check udp ports with the provided ip/host and port/range of ports.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances |
host required | Hostname or an ip address |
port required | Single port, ports separated by comma (eg: 80,81) or a range of ports (eg: 80-85) |
uptime
Run uptime on the specified appliances.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | JSON list of the hostnames of the appliances. |
app-icons
list
List images.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
image_create
Create a new image from a single source image. Most common image formats are supported, like PNG, ICO, JPEG and GIF. The uploaded image should be maximum 100KiB and preferably square. The request body should be a 'multipart/form-data' encoded object (not JSON).
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
file required | Provide the file in the body of the request. |
domain required |
read
Get details of an image.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this image. |
delete
Delete an image.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this image. |
image_update
Updates an existing image from a single source image. Most common image formats are supported, like PNG, ICO, JPEG and GIF. The uploaded image should be maximum 100KiB and preferably square. The request body should be a 'multipart/form-data' encoded object (not JSON).
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this image. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
file required | Provide the file in the body of the request. |
image > read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this image. |
app-servers
list
A list of all application servers. Labels are provided in a list of 'key:value' pairs.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search |
create
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
description | A description of the app server to help with identification. |
domain required | Domain this app server belongs to. |
enabled | Boolean value to define whether the app server can be used. |
host required | The IPv4 address or FQDN of this app server. |
labels required | List with labels in the format key:value that are assigned to this application server. Applications with a matching server label will run on the application server. |
max_connections required | A positive number limiting the number of RDP connections. Use 0 for unlimited connections. |
name required | The name of the app server. |
port required | The port number for the RDP service of the app server (default 3389). |
authentication_protocol | The protocol used for authentication on this app server. |
authentication_host_fqdn | The authentication host (FQDN), needed for Kerberos. |
read
Get a single application server. Labels are provided in a list of 'key:value' pairs.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app server. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search |
update
Update an application server by providing the complete object.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app server. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
description | A description of the app server to help with identification. |
domain required | Domain this app server belongs to. |
enabled | Boolean value to define whether the app server can be used. |
host required | The IPv4 address or FQDN of this app server. |
labels required | List with labels in the format key:value that are assigned to this application server. Applications with a matching server label will run on the application server. |
max_connections required | A positive number limiting the number of RDP connections. Use 0 for unlimited connections. |
name required | The name of the app server. |
port required | The port number for the RDP service of the app server (default 3389). |
authentication_protocol | The protocol used for authentication on this app server. |
authentication_host_fqdn | The authentication host (FQDN), needed for Kerberos. |
partial_update
Update a application server by providing only the changes.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app server. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
description | A description of the app server to help with identification. |
domain | Domain this app server belongs to. |
enabled | Boolean value to define whether the app server can be used. |
host | The IPv4 address or FQDN of this app server. |
labels | List with labels in the format key:value that are assigned to this application server. Applications with a matching server label will run on the application server. |
max_connections | A positive number limiting the number of RDP connections. Use 0 for unlimited connections. |
name | The name of the app server. |
port | The port number for the RDP service of the app server (default 3389). |
authentication_protocol | The protocol used for authentication on this app server. |
authentication_host_fqdn | The authentication host (FQDN), needed for Kerberos. |
delete
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app server. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search |
sessioncount > read
Returns the number of RDP connections to the app-server. There are 4 counters: active (established connections), disconnected (admin has disconnected the connection), reserved (state before established connection), closed (terminated RDP connection; number is cleaned up after a while).
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app server. |
app-sessions
list
List all established connections to the app servers.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
status | |
start | |
end | |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
create
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
app_id required | |
client_ip required | |
dirent | |
gateway_id required | |
rdp_parameters required | |
app_session_id required |
resume
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
app_id required | |
client_ip required | |
dirent | |
gateway_id required | |
rdp_parameters required | |
app_session_id required |
read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
app_session_id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
status | |
start | |
end | |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
update > update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
app_session_id required |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
app_id required | |
client_ip required | |
dirent | |
gateway_id required | |
rdp_parameters required | |
app_session_id required |
update > partial_update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
app_session_id required |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
app_id | |
client_ip | |
dirent | |
gateway_id | |
rdp_parameters | |
app_session_id |
appliances
list
List appliances.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
available
Get all available appliances. Accepts two optional body arguments: ip_address and time_window. Both are mutually exclusive and the default value of time_window is 5 seconds.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
ip_address | IP-address of the appliance to check the availability for. |
time_window | Time window in which available appliances can be discovered. |
appliances_update
Update existing appliances and their services. If changes are made an update (Apply Changes) is triggered.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
appliances required | List of appliances |
dry_run | No actual update is done, only validation. |
accept_service_interruption | Update also if services can be interrupted. |
read
Get details for an appliance.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this appliance. |
current > read
Get details of the current appliance. The current appliance is the one serving the API, thus handling the request.
apps
list
List applications.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
start_in_foreground | Filter on start_in_foreground |
category | |
file_type | |
search |
create
Create a new application. Same rules apply as with update.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
allow_session_merge | Whether or not the app is allowed to be started (merged) in an existing user application session. |
ask_for_credentials | A user will have to provide credentials to start to the application. |
autostart_labels required | List with autostart labels in the format key:value that are assigned to this app. When logging in, users that match one of these labels and have access to this app will start this app automatically. Recorded applications will not be started automatically. |
command | - For protocol "RDP": the command used to start the application (when empty, a full desktop session is started). - For protocol "REMOTE-APP": the alias of the RemoteApp (required). - For protocol "HTTP": the URL to the web application (required); when source_host_header is set, changing this value triggers a limited apply changes on the proxy service. |
concurrent_usage | Whether or not a user is allowed to open multiple instances of this application simultaneously. Cannot be disabled when protocol is "HTTP". |
categories required | List of names of categories this app belongs to. |
description | Description of the application (not shown to the end-user). |
domain required | Domain this application belongs to. |
icon | The URI of the app-icon. |
labels required | List with labels in the format key:value that are assigned to this app. These can be used for organizational purposes or to activate certain features such as smartcard support (by adding the "smartcard:" label) or recording ("record:" label). |
file_types required | List of file extensions (e.g. ["doc", "docx"]). |
name required | Name of the application. |
notifications_enabled | Enables all application notifications. |
protocol required | Protocol of the application. Possible options are: HTTP, RDP or REMOTE-APP. |
working_folder | Working folder into which the application needs to be launched. Only relevant when protocol is "RDP" |
show_in_applications | Whether or not to show this application on the Workspace. |
server_labels required | List with server labels in the format key:value that are assigned to this app. The app will be started on an appserver that also has one of these labels assigned. |
start_in_foreground | When this application is configured to start automatically at login, "start_in_foreground" will make it run in the foreground. Only one application per domain can be configured to start in foreground. Cannot be enabled when protocol is "HTTP". |
supports_unicode_kbd | Whether or not the application supports unicode keyboards, which are better in recognizing special characters. Disable this if typing in the application results in odd behavior (like repetition of the first typed character). |
source_host_header | Setting this field will enable the Workspace to reverse proxy this URL mentioned in the command field. This the hostname shown to the user when opening this HTTP application in their browser (e.g. intranet-pub.mycompany.com). The host header should resolve via DNS to the Workspace, but should be different than the one(s) used to access the Workspace. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
custom_destination_host_header | When use_default_destination_host_header is disabled, the provided host header is passed to the server hosting the HTTP application. A typical use case is to enter the same value of the source_host_header, which means that the server hosting the HTTP application is aware of the presence of a reverse proxy (which might be a configuration option of the HTTP application). Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
enable_max_size | Enable maximum resolution for apps with protocol RDP or REMOTE-APP. When this is enabled the max_height and max_width fields are required. |
enable_min_size | Enable minimum resolution for apps with protocol RDP or REMOTE-APP. When this is enabled the min_height and min_width fields are required. |
max_width | Maximum width for apps with protocol: RDP or REMOTE-APP |
max_height | Maximum height for apps with protocol: RDP or REMOTE-APP |
min_height | Minimum height for apps with protocol: RDP or REMOTE-APP |
min_width | Minimum width for apps with protocol: RDP or REMOTE-APP |
use_default_destination_host_header | If enabled, the host header passed to the server hosting the HTTP application, will be the host name extracted from the url in the command field. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
rewrite | Whether to rewrite all URLs in the returned content (HTTP headers, cookies and text/html body) from the HTTP application by replacing the host of the (custom) destination_host_header with the specified source_host_header. Rewriting is typically needed when the server hosting the HTTP application is not aware that it is reachable through a reverse proxy. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
user_labels required | List with user labels in the format key:value that are assigned to this app. When logging in, only users that match one of these labels will have access to this app. |
printer_driver_name | Determines which printer driver is used when using ' 'the redirected printer. |
color_depth | Defines the color depth of the streamed application. |
reverse_proxy_ssl_server_name | If enabled, we will use Server Name Indication (SNI) when contacting the destination server over HTTPS. Only relevant when protocol is "HTTP" and the destination url starts with "https://". |
reverse_proxy_sso_enabled | If enabled, an HTTP header set by "reverse_proxy_sso_type" field will be passed to the server hosting the HTTP application, enabling SSO for web applications supporting Basic Auth/Remote User. Only relevant when protocol is "HTTP". |
reverse_proxy_sso_type | Type of reverse proxy sso to use. BASIC_AUTH adds Authentication header while REMOTE_USER adds REMOTE_USER header. Only relevant when protocol is "HTTP". |
reverse_proxy_sso_username_type | Format of username that is set in the HTTP header for authentication during SSO. Only relevant when protocol is "HTTP". |
context_labels required | List with context policies in the format key:value that are assigned to this app. Only users that have a context that matches all of these labels will have access to this app. |
read
Get details of an application.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
start_in_foreground | Filter on start_in_foreground |
category | |
file_type | |
search |
update
Update details of an application. The following rules apply: - Command may not be blank when protocol is "HTTP" or "REMOTE-APP". - Concurrent usage can not be disabled when protocol is "HTTP". - Start in foreground can not be enabled when protocol is "HTTP". - Source host header, destination host header and rewrite can only be set when protocol is "HTTP". - Source host header and destination host header must be set or not set together.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
start_in_foreground | Filter on start_in_foreground |
category | |
file_type | |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
allow_session_merge | Whether or not the app is allowed to be started (merged) in an existing user application session. |
ask_for_credentials | A user will have to provide credentials to start to the application. |
autostart_labels required | List with autostart labels in the format key:value that are assigned to this app. When logging in, users that match one of these labels and have access to this app will start this app automatically. Recorded applications will not be started automatically. |
command | - For protocol "RDP": the command used to start the application (when empty, a full desktop session is started). - For protocol "REMOTE-APP": the alias of the RemoteApp (required). - For protocol "HTTP": the URL to the web application (required); when source_host_header is set, changing this value triggers a limited apply changes on the proxy service. |
concurrent_usage | Whether or not a user is allowed to open multiple instances of this application simultaneously. Cannot be disabled when protocol is "HTTP". |
categories required | List of names of categories this app belongs to. |
description | Description of the application (not shown to the end-user). |
domain required | Domain this application belongs to. |
icon | The URI of the app-icon. |
labels required | List with labels in the format key:value that are assigned to this app. These can be used for organizational purposes or to activate certain features such as smartcard support (by adding the "smartcard:" label) or recording ("record:" label). |
file_types required | List of file extensions (e.g. ["doc", "docx"]). |
name required | Name of the application. |
notifications_enabled | Enables all application notifications. |
protocol required | Protocol of the application. Possible options are: HTTP, RDP or REMOTE-APP. |
working_folder | Working folder into which the application needs to be launched. Only relevant when protocol is "RDP" |
show_in_applications | Whether or not to show this application on the Workspace. |
server_labels required | List with server labels in the format key:value that are assigned to this app. The app will be started on an appserver that also has one of these labels assigned. |
start_in_foreground | When this application is configured to start automatically at login, "start_in_foreground" will make it run in the foreground. Only one application per domain can be configured to start in foreground. Cannot be enabled when protocol is "HTTP". |
supports_unicode_kbd | Whether or not the application supports unicode keyboards, which are better in recognizing special characters. Disable this if typing in the application results in odd behavior (like repetition of the first typed character). |
source_host_header | Setting this field will enable the Workspace to reverse proxy this URL mentioned in the command field. This the hostname shown to the user when opening this HTTP application in their browser (e.g. intranet-pub.mycompany.com). The host header should resolve via DNS to the Workspace, but should be different than the one(s) used to access the Workspace. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
custom_destination_host_header | When use_default_destination_host_header is disabled, the provided host header is passed to the server hosting the HTTP application. A typical use case is to enter the same value of the source_host_header, which means that the server hosting the HTTP application is aware of the presence of a reverse proxy (which might be a configuration option of the HTTP application). Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
enable_max_size | Enable maximum resolution for apps with protocol RDP or REMOTE-APP. When this is enabled the max_height and max_width fields are required. |
enable_min_size | Enable minimum resolution for apps with protocol RDP or REMOTE-APP. When this is enabled the min_height and min_width fields are required. |
max_width | Maximum width for apps with protocol: RDP or REMOTE-APP |
max_height | Maximum height for apps with protocol: RDP or REMOTE-APP |
min_height | Minimum height for apps with protocol: RDP or REMOTE-APP |
min_width | Minimum width for apps with protocol: RDP or REMOTE-APP |
use_default_destination_host_header | If enabled, the host header passed to the server hosting the HTTP application, will be the host name extracted from the url in the command field. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
rewrite | Whether to rewrite all URLs in the returned content (HTTP headers, cookies and text/html body) from the HTTP application by replacing the host of the (custom) destination_host_header with the specified source_host_header. Rewriting is typically needed when the server hosting the HTTP application is not aware that it is reachable through a reverse proxy. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
user_labels required | List with user labels in the format key:value that are assigned to this app. When logging in, only users that match one of these labels will have access to this app. |
printer_driver_name | Determines which printer driver is used when using ' 'the redirected printer. |
color_depth | Defines the color depth of the streamed application. |
reverse_proxy_ssl_server_name | If enabled, we will use Server Name Indication (SNI) when contacting the destination server over HTTPS. Only relevant when protocol is "HTTP" and the destination url starts with "https://". |
reverse_proxy_sso_enabled | If enabled, an HTTP header set by "reverse_proxy_sso_type" field will be passed to the server hosting the HTTP application, enabling SSO for web applications supporting Basic Auth/Remote User. Only relevant when protocol is "HTTP". |
reverse_proxy_sso_type | Type of reverse proxy sso to use. BASIC_AUTH adds Authentication header while REMOTE_USER adds REMOTE_USER header. Only relevant when protocol is "HTTP". |
reverse_proxy_sso_username_type | Format of username that is set in the HTTP header for authentication during SSO. Only relevant when protocol is "HTTP". |
context_labels required | List with context policies in the format key:value that are assigned to this app. Only users that have a context that matches all of these labels will have access to this app. |
partial_update
Update some details of an application. Same rules apply as with update.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
start_in_foreground | Filter on start_in_foreground |
category | |
file_type | |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
allow_session_merge | Whether or not the app is allowed to be started (merged) in an existing user application session. |
ask_for_credentials | A user will have to provide credentials to start to the application. |
autostart_labels | List with autostart labels in the format key:value that are assigned to this app. When logging in, users that match one of these labels and have access to this app will start this app automatically. Recorded applications will not be started automatically. |
command | - For protocol "RDP": the command used to start the application (when empty, a full desktop session is started). - For protocol "REMOTE-APP": the alias of the RemoteApp (required). - For protocol "HTTP": the URL to the web application (required); when source_host_header is set, changing this value triggers a limited apply changes on the proxy service. |
concurrent_usage | Whether or not a user is allowed to open multiple instances of this application simultaneously. Cannot be disabled when protocol is "HTTP". |
categories | List of names of categories this app belongs to. |
description | Description of the application (not shown to the end-user). |
domain | Domain this application belongs to. |
icon | The URI of the app-icon. |
labels | List with labels in the format key:value that are assigned to this app. These can be used for organizational purposes or to activate certain features such as smartcard support (by adding the "smartcard:" label) or recording ("record:" label). |
file_types | List of file extensions (e.g. ["doc", "docx"]). |
name | Name of the application. |
notifications_enabled | Enables all application notifications. |
protocol | Protocol of the application. Possible options are: HTTP, RDP or REMOTE-APP. |
working_folder | Working folder into which the application needs to be launched. Only relevant when protocol is "RDP" |
show_in_applications | Whether or not to show this application on the Workspace. |
server_labels | List with server labels in the format key:value that are assigned to this app. The app will be started on an appserver that also has one of these labels assigned. |
start_in_foreground | When this application is configured to start automatically at login, "start_in_foreground" will make it run in the foreground. Only one application per domain can be configured to start in foreground. Cannot be enabled when protocol is "HTTP". |
supports_unicode_kbd | Whether or not the application supports unicode keyboards, which are better in recognizing special characters. Disable this if typing in the application results in odd behavior (like repetition of the first typed character). |
source_host_header | Setting this field will enable the Workspace to reverse proxy this URL mentioned in the command field. This the hostname shown to the user when opening this HTTP application in their browser (e.g. intranet-pub.mycompany.com). The host header should resolve via DNS to the Workspace, but should be different than the one(s) used to access the Workspace. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
custom_destination_host_header | When use_default_destination_host_header is disabled, the provided host header is passed to the server hosting the HTTP application. A typical use case is to enter the same value of the source_host_header, which means that the server hosting the HTTP application is aware of the presence of a reverse proxy (which might be a configuration option of the HTTP application). Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
enable_max_size | Enable maximum resolution for apps with protocol RDP or REMOTE-APP. When this is enabled the max_height and max_width fields are required. |
enable_min_size | Enable minimum resolution for apps with protocol RDP or REMOTE-APP. When this is enabled the min_height and min_width fields are required. |
max_width | Maximum width for apps with protocol: RDP or REMOTE-APP |
max_height | Maximum height for apps with protocol: RDP or REMOTE-APP |
min_height | Minimum height for apps with protocol: RDP or REMOTE-APP |
min_width | Minimum width for apps with protocol: RDP or REMOTE-APP |
use_default_destination_host_header | If enabled, the host header passed to the server hosting the HTTP application, will be the host name extracted from the url in the command field. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
rewrite | Whether to rewrite all URLs in the returned content (HTTP headers, cookies and text/html body) from the HTTP application by replacing the host of the (custom) destination_host_header with the specified source_host_header. Rewriting is typically needed when the server hosting the HTTP application is not aware that it is reachable through a reverse proxy. Triggers a limited apply changes on the proxy service. Only relevant when protocol is "HTTP". |
user_labels | List with user labels in the format key:value that are assigned to this app. When logging in, only users that match one of these labels will have access to this app. |
printer_driver_name | Determines which printer driver is used when using ' 'the redirected printer. |
color_depth | Defines the color depth of the streamed application. |
reverse_proxy_ssl_server_name | If enabled, we will use Server Name Indication (SNI) when contacting the destination server over HTTPS. Only relevant when protocol is "HTTP" and the destination url starts with "https://". |
reverse_proxy_sso_enabled | If enabled, an HTTP header set by "reverse_proxy_sso_type" field will be passed to the server hosting the HTTP application, enabling SSO for web applications supporting Basic Auth/Remote User. Only relevant when protocol is "HTTP". |
reverse_proxy_sso_type | Type of reverse proxy sso to use. BASIC_AUTH adds Authentication header while REMOTE_USER adds REMOTE_USER header. Only relevant when protocol is "HTTP". |
reverse_proxy_sso_username_type | Format of username that is set in the HTTP header for authentication during SSO. Only relevant when protocol is "HTTP". |
context_labels | List with context policies in the format key:value that are assigned to this app. Only users that have a context that matches all of these labels will have access to this app. |
delete
Delete an application.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this app. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
start_in_foreground | Filter on start_in_foreground |
category | |
file_type | |
search |
auth-providers
list
List authentication providers.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
domain_name | Domain name to filter on. |
key | Key to filter on. |
domain | Domain id to filter on. |
read
Get details for an authentication provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
key | Key to filter on. |
domain | Domain id to filter on. |
update
Update details for an authentication provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
key | Key to filter on. |
domain | Domain id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
config required | Configuration for this authentication provider. Only the value of each configuration item can be changed, and only when it is not read-only. |
partial_update
Update details for an authentication provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
key | Key to filter on. |
domain | Domain id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
config | Configuration for this authentication provider. Only the value of each configuration item can be changed, and only when it is not read-only. |
bookmarks
list
List bookmarks, which can be filtered with the parameter "user"
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
user | User id to filter on. |
create
Create a new bookmark.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
dirent required | The URI of the file or folder where the bookmark points to |
move_down
Move target bookmark index down by one.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
bookmark required | Bookmark to move. |
move_to
Move target bookmark index to given index.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
bookmark required | Bookmark to move. |
index required | Index to move the bookmark to. |
move_up
Move target bookmark index up by one.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
bookmark required | Bookmark to move. |
read
Get details of a bookmark.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this bookmark. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
delete
Delete a bookmark.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this bookmark. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
branding
list
List branding configurations.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
generate_pre_auth_url
Returns pre_auth_url for domain (via host headers) if configured for that domain. e.g. /api/v2/branding/generate-pre-auth-url
read
Get branding configuration details.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this branding. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
update
Update branding configuration.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this branding. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
background_type | Background types (PLAIN-COLOR or POLYGON) |
custom_desktop_background | Branding image URI of the custom desktop background (max. 500 KiB). |
custom_logo | Branding image URI of the custom wide logo (max. 100 KiB). The wide logo is used in the expanded sidebar. |
custom_tablet_background | Branding image URI of the custom tablet background (max. 150 KiB). |
login_footer | Login footer. |
primary_color required | A hex color value in string format starting with a pound sign. Eg. #FFFFFF. |
secondary_color required | A hex color value in string format starting with a pound sign. Eg. #FFFFFF. |
use_custom_favicon | Flag indicating whether to use the custom favicon or not. |
use_custom_login_background | Flag indicating whether to use the custom login backgroundor not. |
use_custom_logo | Flag indicating whether to use the custom logo or not. |
partial_update
Partially update branding.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this branding. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
background_type | Background types (PLAIN-COLOR or POLYGON) |
custom_desktop_background | Branding image URI of the custom desktop background (max. 500 KiB). |
custom_logo | Branding image URI of the custom wide logo (max. 100 KiB). The wide logo is used in the expanded sidebar. |
custom_tablet_background | Branding image URI of the custom tablet background (max. 150 KiB). |
login_footer | Login footer. |
primary_color | A hex color value in string format starting with a pound sign. Eg. #FFFFFF. |
secondary_color | A hex color value in string format starting with a pound sign. Eg. #FFFFFF. |
use_custom_favicon | Flag indicating whether to use the custom favicon or not. |
use_custom_login_background | Flag indicating whether to use the custom login backgroundor not. |
use_custom_logo | Flag indicating whether to use the custom logo or not. |
branding-images
list
List branding images.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
image_create
Create a new branding image from a single source image. Most common image formats are supported, like PNG, JPEG and GIF. The uploaded image should be maximum 500KiB. The request body should be a 'multipart/form-data' encoded object (not JSON).
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
domain required | Domain this image belongs to. |
file required | Provide the file in the body of the request. |
read
Get branding image details.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this branding image. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
delete
Delete branding image.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this branding image. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
image_update
Updates an existing branding image from a single source image. Most common image formats are supported, like PNG, JPEG and GIF. The uploaded image should be maximum 500KiB. The request body should be a 'multipart/form-data' encoded object (not JSON).
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this branding image. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
file required | Provide the file in the body of the request. |
image > read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this branding image. |
categories
list
List categories, which are used to group applications.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
create
Create a new category. Categories are used to group applications.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
name required | Name of the category |
domain required |
read
Get details of a category. Categories are used to group applications.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this category. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
update
Update details of a category. Categories are used to group applications.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this category. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
name required | Name of the category |
domain required |
partial_update
Update some details of a category. Categories are used to group applications.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this category. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
name | Name of the category |
domain |
delete
Delete a category. Categories are used to group applications. Deleting a category will not delete the applications linked to it.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this category. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
name | Name to filter on. |
configuration
list
List global configurations for your Workspace. Currently there will always be only one configuration.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
check_license
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
snmp_password | Password for SNMP. Must be between 8 and 32 characters long. Required if SNMP is enabled. Triggers a limited apply changes on the SNMP service. |
hsts_enabled | Informs the browsers that the Workspace should only be accessed using HTTPS, and that any future attempts to access it using HTTP should automatically be converted to HTTPS. Can only be enabled if ssl_mode is EXTERNAL or ENFORCED and hsts_max_age is set. |
dbadmin_whitelisted_subnets_enabled | Whether or not subnet whitelisting is enabled for the local admin account. |
upgrade_message_dismissed | Whether or not to stop showing an upgrade message. |
hsts_max_age | The time, in seconds, that the browser should remember that the Workspace is only accessible using HTTPS. |
license | License file as supplied by your Partner. |
dns_ip required | A comma separated list of IPv4 addresses of DNS servers to be used for all external DNS resolving by this Workspace. Triggers a limited apply changes on the DNS service. |
system_message_enabled | Whether or not to show the message in system_message. |
ssl_mode | Mode of the internal SSL offloader. The choices are OPTIONAL, ENFORCED and EXTERNAL. OPTIONAL means you can access the Workspace through both HTTP and HTTPS, but the specific security measurements for HTTPS (e.g. Cookie Secure Flag) won't be applied. This setting can be used with both the internal and an external SSL offloader. ENFORCED means that all HTTP traffic to the Workspace will be redirected to HTTPS, which will be handled by the internal SSL offloader. This enables specific security measurements for HTTPS (e.g. Cookie Secure Flag). EXTERNAL means that the Workspace accepts non-SSL traffic, but specific security measurements for HTTPS (e.g. Cookie Secure Flag) will be enforced. With EXTERNAL you need an external SSL offloader to access the Workspace. Triggers a limited apply changes on the proxy service. |
hsts_preload | When enabled, the Workspace URL can be submitted to the HSTS preload list. To be accepted to the list other requirements also need to be met. |
sftp_password | Password to use for SFTP access to the environment backups on the appliances. Must have a minimum length of 8 characters. Triggers a limited apply changes on the SFTP user. |
hsts_include_subdomains | Determines if the HSTS header is also active on all of the website's subdomains. |
proxy_url | The URL of the HTTP proxy to be used, formatted as http(s)://username:password@fqdn_or_ip:port. Username and password are optional. Mandatory if the HTTP proxy is enabled. Note that upgrades, anonymous data collection and some MFA providers require outgoing HTTP requests. Triggers a limited apply changes on the HTTP proxy service. |
backup_encryption_password | Password to use to encrypt the environment backups. While this password is not set, backups will not be encrypted. Encrypted backups have the '.enc' extension and will require this same password to be able to restore the backup. |
log_level_application_gateway | Application gateway log level. |
snmp_enabled | Whether or not SNMP v3 is enabled for this Workspace. If enabled, snmp_password is required to be filled in. Triggers a limited apply changes on the SNMP service. |
backup_time | Time in UTC when the daily environment backup will start. |
ntp_server required | A comma separated list of FQDNs or IPv4 addresses of NTP servers, used by this Workspace to synchronize its internal clock. If NTP is provided by DHCP, this setting will be ignored. Triggers a limited apply changes on the NTP service. |
repo_url | URL of the repository server used to keep this Workspace up to date. Triggers a limited apply changes on the APT sources. |
vault_backup_enabled | Whether or not to enable backups of the Vault service. There can be a short service interruption for SSO starting at the daily backup_time if this is enabled. If Vault is not included in the backup, SSO will fall back to pre-authentication when restoring from this backup.This option has no effect if no seal provider has been selected. |
system_message | Message that is shown to logged-in users if system_message_enabled is True. |
app_session_failover | Whether or not to failover application sessions when a node goes down |
seal_provider | |
trusted_ca | Global level trusted Certificate Authorities |
license_enabled | |
default_domain | Domain that is used by default when no other domain has been selected. |
anonymous_reporting_enabled | Whether or not anonymized data is collected on this Workspace. If set to null, the System Settings will ask the administrator to make a choice next time he opens the System Settings. No data will be collected as long as this setting is set to null or false. |
proxy_enabled | Whether or not an HTTP proxy is used for all outgoing HTTP requests. Triggers a limited apply changes on the HTTP proxy service. |
dbadmin_whitelisted_subnets | List of IPv4 subnets from which clients are allowed to login with the local admin account. |
feature_flags required | |
reverse_proxy_subnets | List of IPv4 subnets that are considered to be reverse proxies by the Workspace. |
basic_sso_enabled | Whether or not Basic SSO integration is enabled (for Pulse Connect Secure). Triggers a limited apply changes on the proxy service. |
client_ip
Internal API call so the gateway can determine if it should use the value of the X-Forwarded-For header or the actual remote address connecting to the Workspace.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
remote_address required | |
forwarded_address |
decode_license
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
license required |
disable_intervention_password
Disables the intervention password so it is not required anymore for interventions by the Support Team. The support team still needs to use their SSH keypair to login, and to have network access on the SSH port.
generate_intervention_password
Generate a new intervention password. This will replace any previous intervention passwords. Please don't lose the generated intervention code! Without the code, you cannot get any remote support from the Support Team anymore. It is recommended to only set an intervention code when you have opened the SSH port on your firewall and to disable the intervention code once the SSH port has been closed.
read
Get global configuration details for your Workspace.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this configuration. |
update
Change global configuration for your Workspace. Changes to some of these fields will trigger a limited apply changes automatically. This is indicated in the per-field documentation. During this apply changes the SMC interface is unavailable. You can follow the progress of this apply changes using the Update API.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this configuration. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
snmp_password | Password for SNMP. Must be between 8 and 32 characters long. Required if SNMP is enabled. Triggers a limited apply changes on the SNMP service. |
hsts_enabled | Informs the browsers that the Workspace should only be accessed using HTTPS, and that any future attempts to access it using HTTP should automatically be converted to HTTPS. Can only be enabled if ssl_mode is EXTERNAL or ENFORCED and hsts_max_age is set. |
dbadmin_whitelisted_subnets_enabled | Whether or not subnet whitelisting is enabled for the local admin account. |
upgrade_message_dismissed | Whether or not to stop showing an upgrade message. |
hsts_max_age | The time, in seconds, that the browser should remember that the Workspace is only accessible using HTTPS. |
license | License file as supplied by your Partner. |
dns_ip required | A comma separated list of IPv4 addresses of DNS servers to be used for all external DNS resolving by this Workspace. Triggers a limited apply changes on the DNS service. |
system_message_enabled | Whether or not to show the message in system_message. |
ssl_mode | Mode of the internal SSL offloader. The choices are OPTIONAL, ENFORCED and EXTERNAL. OPTIONAL means you can access the Workspace through both HTTP and HTTPS, but the specific security measurements for HTTPS (e.g. Cookie Secure Flag) won't be applied. This setting can be used with both the internal and an external SSL offloader. ENFORCED means that all HTTP traffic to the Workspace will be redirected to HTTPS, which will be handled by the internal SSL offloader. This enables specific security measurements for HTTPS (e.g. Cookie Secure Flag). EXTERNAL means that the Workspace accepts non-SSL traffic, but specific security measurements for HTTPS (e.g. Cookie Secure Flag) will be enforced. With EXTERNAL you need an external SSL offloader to access the Workspace. Triggers a limited apply changes on the proxy service. |
hsts_preload | When enabled, the Workspace URL can be submitted to the HSTS preload list. To be accepted to the list other requirements also need to be met. |
sftp_password | Password to use for SFTP access to the environment backups on the appliances. Must have a minimum length of 8 characters. Triggers a limited apply changes on the SFTP user. |
hsts_include_subdomains | Determines if the HSTS header is also active on all of the website's subdomains. |
proxy_url | The URL of the HTTP proxy to be used, formatted as http(s)://username:password@fqdn_or_ip:port. Username and password are optional. Mandatory if the HTTP proxy is enabled. Note that upgrades, anonymous data collection and some MFA providers require outgoing HTTP requests. Triggers a limited apply changes on the HTTP proxy service. |
backup_encryption_password | Password to use to encrypt the environment backups. While this password is not set, backups will not be encrypted. Encrypted backups have the '.enc' extension and will require this same password to be able to restore the backup. |
log_level_application_gateway | Application gateway log level. |
snmp_enabled | Whether or not SNMP v3 is enabled for this Workspace. If enabled, snmp_password is required to be filled in. Triggers a limited apply changes on the SNMP service. |
backup_time | Time in UTC when the daily environment backup will start. |
ntp_server required | A comma separated list of FQDNs or IPv4 addresses of NTP servers, used by this Workspace to synchronize its internal clock. If NTP is provided by DHCP, this setting will be ignored. Triggers a limited apply changes on the NTP service. |
repo_url | URL of the repository server used to keep this Workspace up to date. Triggers a limited apply changes on the APT sources. |
vault_backup_enabled | Whether or not to enable backups of the Vault service. There can be a short service interruption for SSO starting at the daily backup_time if this is enabled. If Vault is not included in the backup, SSO will fall back to pre-authentication when restoring from this backup.This option has no effect if no seal provider has been selected. |
system_message | Message that is shown to logged-in users if system_message_enabled is True. |
app_session_failover | Whether or not to failover application sessions when a node goes down |
seal_provider | |
trusted_ca | Global level trusted Certificate Authorities |
license_enabled | |
default_domain | Domain that is used by default when no other domain has been selected. |
anonymous_reporting_enabled | Whether or not anonymized data is collected on this Workspace. If set to null, the System Settings will ask the administrator to make a choice next time he opens the System Settings. No data will be collected as long as this setting is set to null or false. |
proxy_enabled | Whether or not an HTTP proxy is used for all outgoing HTTP requests. Triggers a limited apply changes on the HTTP proxy service. |
dbadmin_whitelisted_subnets | List of IPv4 subnets from which clients are allowed to login with the local admin account. |
feature_flags required | |
reverse_proxy_subnets | List of IPv4 subnets that are considered to be reverse proxies by the Workspace. |
basic_sso_enabled | Whether or not Basic SSO integration is enabled (for Pulse Connect Secure). Triggers a limited apply changes on the proxy service. |
partial_update
Change some fields of the global configuration for your Workspace. Changes to some of these fields will trigger a limited apply changes automatically. This is indicated in the per-field documentation. During this apply changes the SMC interface is unavailable. You can follow the progress of this apply changes using the Update API.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this configuration. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
snmp_password | Password for SNMP. Must be between 8 and 32 characters long. Required if SNMP is enabled. Triggers a limited apply changes on the SNMP service. |
hsts_enabled | Informs the browsers that the Workspace should only be accessed using HTTPS, and that any future attempts to access it using HTTP should automatically be converted to HTTPS. Can only be enabled if ssl_mode is EXTERNAL or ENFORCED and hsts_max_age is set. |
dbadmin_whitelisted_subnets_enabled | Whether or not subnet whitelisting is enabled for the local admin account. |
upgrade_message_dismissed | Whether or not to stop showing an upgrade message. |
hsts_max_age | The time, in seconds, that the browser should remember that the Workspace is only accessible using HTTPS. |
license | License file as supplied by your Partner. |
dns_ip | A comma separated list of IPv4 addresses of DNS servers to be used for all external DNS resolving by this Workspace. Triggers a limited apply changes on the DNS service. |
system_message_enabled | Whether or not to show the message in system_message. |
ssl_mode | Mode of the internal SSL offloader. The choices are OPTIONAL, ENFORCED and EXTERNAL. OPTIONAL means you can access the Workspace through both HTTP and HTTPS, but the specific security measurements for HTTPS (e.g. Cookie Secure Flag) won't be applied. This setting can be used with both the internal and an external SSL offloader. ENFORCED means that all HTTP traffic to the Workspace will be redirected to HTTPS, which will be handled by the internal SSL offloader. This enables specific security measurements for HTTPS (e.g. Cookie Secure Flag). EXTERNAL means that the Workspace accepts non-SSL traffic, but specific security measurements for HTTPS (e.g. Cookie Secure Flag) will be enforced. With EXTERNAL you need an external SSL offloader to access the Workspace. Triggers a limited apply changes on the proxy service. |
hsts_preload | When enabled, the Workspace URL can be submitted to the HSTS preload list. To be accepted to the list other requirements also need to be met. |
sftp_password | Password to use for SFTP access to the environment backups on the appliances. Must have a minimum length of 8 characters. Triggers a limited apply changes on the SFTP user. |
hsts_include_subdomains | Determines if the HSTS header is also active on all of the website's subdomains. |
proxy_url | The URL of the HTTP proxy to be used, formatted as http(s)://username:password@fqdn_or_ip:port. Username and password are optional. Mandatory if the HTTP proxy is enabled. Note that upgrades, anonymous data collection and some MFA providers require outgoing HTTP requests. Triggers a limited apply changes on the HTTP proxy service. |
backup_encryption_password | Password to use to encrypt the environment backups. While this password is not set, backups will not be encrypted. Encrypted backups have the '.enc' extension and will require this same password to be able to restore the backup. |
log_level_application_gateway | Application gateway log level. |
snmp_enabled | Whether or not SNMP v3 is enabled for this Workspace. If enabled, snmp_password is required to be filled in. Triggers a limited apply changes on the SNMP service. |
backup_time | Time in UTC when the daily environment backup will start. |
ntp_server | A comma separated list of FQDNs or IPv4 addresses of NTP servers, used by this Workspace to synchronize its internal clock. If NTP is provided by DHCP, this setting will be ignored. Triggers a limited apply changes on the NTP service. |
repo_url | URL of the repository server used to keep this Workspace up to date. Triggers a limited apply changes on the APT sources. |
vault_backup_enabled | Whether or not to enable backups of the Vault service. There can be a short service interruption for SSO starting at the daily backup_time if this is enabled. If Vault is not included in the backup, SSO will fall back to pre-authentication when restoring from this backup.This option has no effect if no seal provider has been selected. |
system_message | Message that is shown to logged-in users if system_message_enabled is True. |
app_session_failover | Whether or not to failover application sessions when a node goes down |
seal_provider | |
trusted_ca | Global level trusted Certificate Authorities |
license_enabled | |
default_domain | Domain that is used by default when no other domain has been selected. |
anonymous_reporting_enabled | Whether or not anonymized data is collected on this Workspace. If set to null, the System Settings will ask the administrator to make a choice next time he opens the System Settings. No data will be collected as long as this setting is set to null or false. |
proxy_enabled | Whether or not an HTTP proxy is used for all outgoing HTTP requests. Triggers a limited apply changes on the HTTP proxy service. |
dbadmin_whitelisted_subnets | List of IPv4 subnets from which clients are allowed to login with the local admin account. |
feature_flags | |
reverse_proxy_subnets | List of IPv4 subnets that are considered to be reverse proxies by the Workspace. |
basic_sso_enabled | Whether or not Basic SSO integration is enabled (for Pulse Connect Secure). Triggers a limited apply changes on the proxy service. |
configuration-info
list
Public read-only view of a subset of the configuration. Currently this is only used to be able to show the licensed customer on the login page.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
read
Public read-only view of a subset of the configuration. Currently this is only used to be able to show the licensed customer on the login page.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this configuration. |
contacts
list
List of contact informations. For informational purposes only.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
read
Get information of a contact. For informational purposes only.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this contact. |
update
Update information of a contact. For informational purposes only.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this contact. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
address_line_1 required | |
address_line_2 required | |
city | City or place name. |
country | Country. |
location | State or province. |
name | Name. |
phone_number | International phone number. Must start with "+", followed by digits. |
postal_code | Postal code. |
partial_update
Update information of a contact. For informational purposes only.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this contact. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
address_line_1 | |
address_line_2 | |
city | City or place name. |
country | Country. |
location | State or province. |
name | Name. |
phone_number | International phone number. Must start with "+", followed by digits. |
postal_code | Postal code. |
domains
list
List domains.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
name | Domain name to filter on. |
search |
create
Create a new domain.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
admin_user_labels | List with labels in the format key:value that are used todefine which users have admin credentials. |
admin_context_labels | List with labels in the format key:value. These can be used for context awareness. |
app_session_upload_enabled | Whether or not application session are recorded. The recordings are uploaded to the remote server specified by app_session_upload_url. |
app_session_upload_url | URL of the fileserver to upload application session recordings to. Both WebDAV and SMB/CIFS fileservers are supported. For WebDAV, the URL structure is: http(s)://username:password@fqdn_or_ip/path/to/destination. For SMB/CIFS, the URL structure is smb://domain\username:password@fqdn_or_ip/share_name/path/to/destination. Recordings that cannot be uploaded will be removed after seven days. |
app_session_upload_use_domain_fqdn | If True, the domain FQDN will be used in the username when contacting the SMB/CIFS fileserver. If False, the domain netbios will be used instead. |
app_session_keepalive_timeout | Maximum time in minutes that disconnected application sessions are kept alive on the backend. Must be at least one 1 minute and at most 24 hours. Requires a manual apply changes using the Update API. |
base_dn required | Used to bind to the Domain Controller or LDAP Server. E.g.: dc=domain,dc=local |
bind_name | Username used for import of labels (groups and users) and application servers. It is also used to fetch a user's objectSid attribute from the DC/LDAP server when SSO is enabled. |
bind_password | Password used for import of labels (groups and users) and application servers. It is also used to fetch a user's objectSid attribute from DC/LDAP server when SSO is enabled. |
create_bind_name | Advanced setting to configure the function for "Create Bind Name". |
default_keyboard_layout | Default keyboard layout for new users from this domain. |
default_locale | This language is used as fall-back when the browser of the user does not support any of the languages. |
default_tours_enabled | Enable/disable guided tours for all new users of this domain. Users can still manually enable/disable guided tours from their user profile. |
default_polygon_enabled | Enable/disable polygon for all new users of this domain. Users can still manually enable/disable polygon from their user profile. |
default_profile_update_required | When set a profile update is required at next sign in for all new users of this domain. |
dns_servers | Comma separated list of IP addresses of the DNS server(s) used to resolve hostnames connected to this domain. Is typically equal to the IP(s) of the Domain Controller(s). E.g.: 172.1.0.1,172.1.0.2 |
external_audit_enabled | Enable to sent audit logs to external audit system |
external_audit_url | The external audit URL. This is used to sent audit logs the external audit system. |
external_audit_basic_auth_enabled | When enabled an authorization header will be added to requests made to the external_audit_url |
external_audit_username | Username used when Basic Auth is enabled for external audit |
external_audit_password | Password used when Basic Auth is enabled for external audit |
find_groups | Advanced setting to configure the function for "Find Groups". |
fqdn required | Used to sign in with e-mail address like user name. And for direct tcp SMB authentication. E.g. domain.local |
is_admin | When set to true, admin users of this domain are allowed to configure all domains, global settings and have access to the Dashboard. |
ldap_ssl_enabled | Is required to allow users to change their password via the Workspace. Requires SSL certificate on Domain Controller or LDAP Server. |
local_clipboard_push_max_size | Maximum size in MB of data that can be pushed to the local clipboard, per clipboard data type. Must be minimum 5 and maximum 50 MB. This setting only applies to the async clipboard implementation. |
max_licensed | The maximum number of users from this domain that can be signed in to the Workspace at the same time (concurrent users license), or the maximum number of users a domain may have (named users license).Only used when max_licensed_enabled is set to true. |
max_licensed_enabled | Whether to limit the number of users from this domain that are signed in at the same time (concurrent users license) or the maximum number of users a domain may have (named users license). |
name required | Domain name used in the Workspace. Multiple names can refer to the same NetBIOS name. |
netbios required | NetBIOS name of the domain on the Domain Controller or LDAP Server. |
recorded_user_labels | List with labels in the format key:value that are used todefine which sessions must be recorded. |
server required | One or more (comma-separated) IPv4 addresses or FQDN's of the Domain Controller or LDAP Server. E.g. ad01.domain.local |
sign_in_user_labels | List with labels in the format key:value that are used towhitelist users to sign in when whitelisting is enabled. |
sign_in_context_labels | List with labels in the format key:value. These can be used for context awareness. |
twofactor | URI to a twofactor-provider. Set to none if no twofactor-provider is configured. |
twofactor_trusted_browser_enabled | If enabled, users will be allowed to mark a browser as "trusted", so an MFA token is not required for the next 30 days. |
twofactor_whitelisted_subnets | List of IPv4 subnets that do not have to perform MFA in order to sign in to the Workspace using this domain. |
twofactor_whitelisted_labels | List with labels in the format key:value that are used toexempt users from doing MFA login. |
auth_provider | URI to a auth-provider. Set to none if no auth-provider is configured. |
workspace_url | The Workspace base URL. This is used to construct the redirect URL for the Authentication Provider. |
default_host_header | |
privacy_policy_acceptance_required | If enabled (default), each user will have to accept the Privacy Policy the first time they sign in. Disabling means that this domain is not GDPR (European General Data Protection Regulation) compliant. |
apitoken_whitelisted_subnets_enabled | If enabled, api calls using token authentication can only be done from the whitelisted subnets. |
apitoken_whitelisted_subnets | List of IPv4 subnets that can perform api calls using token authentication when enabled. |
change_password_failed_msg_enabled | If enabled, a message set by the admin will also be added to the api response |
change_password_failed_msg | Set a custom password to show to user when they failed to change their password. |
sso_enabled | Enable to for SSO with external IDP |
sso_ca_certificate | Certificate Authority certificate for SSO |
sso_ca_private_key | |
sso_ca_crl_distribution_point | CRL distribution point URL for SSO |
sso_ca_aia_issuers | AIA CA issuers URL for SSO |
sso_trusted_roots | Trusted roots for kerberos authentication for SSO. |
sso_ca_cert_pkcs_12_file | PKCS12 file containing ca certificate and ca private key.Overwrites sso_ca_certificate/sso_ca_private_key if these are also supplied |
sso_ca_cert_pkcs_12_pwd | Password protecting the ca cert/key PKCS12 file. |
sso_trusted_roots_pkcs_12_file | PKCS12 file containing trusted roots. Overwrites sso_trusted_roots if it was also supplied |
sso_trusted_roots_pkcs_12_pwd | Password protecting the trusted roots PKCS12 file. |
use_legacy_clipboard_implementation | Force all applications to use the legacy clipboard implementation. |
use_legacy_keyboard_implementation | Force all applications to use the legacy keyboard implementation. |
async_clipboard_timeout | Timeout (in seconds) to wait for responses from the client or the application server in the new async clipboard implementation. Users will need to log out and back in to apply a new timeout to their application sessions. |
auto_sign_out_enabled | Automatically sign out users inactive for a pre-defined amount of time. |
auto_sign_out_timeout | Timeout (in seconds) to wait before signing out an inactive user. |
auto_sign_out_labels | List with labels in the format key:value that are used to define for which users the auto sign out setting applies. |
trusted_ca | Domain level trusted Certificate Authorities |
ssl_verification_external_audit | Enable SSL verification for External Audit Logging. |
ssl_verification_reverse_proxy | Enable SSL verification for Reverse Proxied Web Applications. |
ssl_verification_webdav | Enable SSL verification for WebDAV. |
ssl_verification_pre_auth | Enable SSL verification for Pre-auth/SSO metadata. |
read
Get details for a domain.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this domain. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
name | Domain name to filter on. |
search |
update
Update details for a domain. The name cannot be changed on an existing domain. Only global administrators can configure all fields; domain administrators can only configure a subset of fields (cf. the returned fields when reading a domain).
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this domain. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
name | Domain name to filter on. |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
admin_context_labels | List with labels in the format key:value. These can be used for context awareness. |
admin_user_labels | List with labels in the format key:value that are used todefine which users have admin credentials. |
apitoken_whitelisted_subnets | List of IPv4 subnets that can perform api calls using token authentication when enabled. |
apitoken_whitelisted_subnets_enabled | If enabled, api calls using token authentication can only be done from the whitelisted subnets. |
app_session_keepalive_timeout | Maximum time in minutes that disconnected application sessions are kept alive on the backend. Must be at least one 1 minute and at most 24 hours. Requires a manual apply changes using the Update API. |
app_session_upload_enabled | Whether or not application session are recorded. The recordings are uploaded to the remote server specified by app_session_upload_url. |
app_session_upload_url | URL of the fileserver to upload application session recordings to. Both WebDAV and SMB/CIFS fileservers are supported. For WebDAV, the URL structure is: http(s)://username:password@fqdn_or_ip/path/to/destination. For SMB/CIFS, the URL structure is smb://domain\username:password@fqdn_or_ip/share_name/path/to/destination. Recordings that cannot be uploaded will be removed after seven days. |
app_session_upload_use_domain_fqdn | If True, the domain FQDN will be used in the username when contacting the SMB/CIFS fileserver. If False, the domain netbios will be used instead. |
async_clipboard_timeout | Timeout (in seconds) to wait for responses from the client or the application server in the new async clipboard implementation. Users will need to log out and back in to apply a new timeout to their application sessions. |
auth_provider | URI to a auth-provider. Set to none if no auth-provider is configured. |
auto_sign_out_enabled | Automatically sign out users inactive for a pre-defined amount of time. |
auto_sign_out_labels | List with labels in the format key:value that are used to define for which users the auto sign out setting applies. |
auto_sign_out_timeout | Timeout (in seconds) to wait before signing out an inactive user. |
base_dn required | Used to bind to the Domain Controller or LDAP Server. E.g.: dc=domain,dc=local |
bind_name | Username used for import of labels (groups and users) and application servers. It is also used to fetch a user's objectSid attribute from the DC/LDAP server when SSO is enabled. |
bind_password | Password used for import of labels (groups and users) and application servers. It is also used to fetch a user's objectSid attribute from DC/LDAP server when SSO is enabled. |
change_password_failed_msg | Set a custom password to show to user when they failed to change their password. |
change_password_failed_msg_enabled | If enabled, a message set by the admin will also be added to the api response |
create_bind_name | Advanced setting to configure the function for "Create Bind Name". |
default_host_header | |
default_keyboard_layout | Default keyboard layout for new users from this domain. |
default_locale | This language is used as fall-back when the browser of the user does not support any of the languages. |
default_polygon_enabled | Enable/disable polygon for all new users of this domain. Users can still manually enable/disable polygon from their user profile. |
default_profile_update_required | When set a profile update is required at next sign in for all new users of this domain. |
default_tours_enabled | Enable/disable guided tours for all new users of this domain. Users can still manually enable/disable guided tours from their user profile. |
dns_servers | Comma separated list of IP addresses of the DNS server(s) used to resolve hostnames connected to this domain. Is typically equal to the IP(s) of the Domain Controller(s). E.g.: 172.1.0.1,172.1.0.2 |
external_audit_basic_auth_enabled | When enabled an authorization header will be added to requests made to the external_audit_url |
external_audit_enabled | Enable to sent audit logs to external audit system |
external_audit_password | Password used when Basic Auth is enabled for external audit |
external_audit_url | The external audit URL. This is used to sent audit logs the external audit system. |
external_audit_username | Username used when Basic Auth is enabled for external audit |
find_groups | Advanced setting to configure the function for "Find Groups". |
fqdn required | Used to sign in with e-mail address like user name. And for direct tcp SMB authentication. E.g. domain.local |
is_admin | When set to true, admin users of this domain are allowed to configure all domains, global settings and have access to the Dashboard. |
ldap_ssl_enabled | Is required to allow users to change their password via the Workspace. Requires SSL certificate on Domain Controller or LDAP Server. |
local_clipboard_push_max_size | Maximum size in MB of data that can be pushed to the local clipboard, per clipboard data type. Must be minimum 5 and maximum 50 MB. This setting only applies to the async clipboard implementation. |
max_licensed | The maximum number of users from this domain that can be signed in to the Workspace at the same time (concurrent users license), or the maximum number of users a domain may have (named users license).Only used when max_licensed_enabled is set to true. |
max_licensed_enabled | Whether to limit the number of users from this domain that are signed in at the same time (concurrent users license) or the maximum number of users a domain may have (named users license). |
netbios required | NetBIOS name of the domain on the Domain Controller or LDAP Server. |
privacy_policy_acceptance_required | If enabled (default), each user will have to accept the Privacy Policy the first time they sign in. Disabling means that this domain is not GDPR (European General Data Protection Regulation) compliant. |
recorded_user_labels | List with labels in the format key:value that are used todefine which sessions must be recorded. |
server required | One or more (comma-separated) IPv4 addresses or FQDN's of the Domain Controller or LDAP Server. E.g. ad01.domain.local |
sign_in_context_labels | List with labels in the format key:value. These can be used for context awareness. |
sign_in_user_labels | List with labels in the format key:value that are used towhitelist users to sign in when whitelisting is enabled. |
ssl_verification_external_audit | Enable SSL verification for External Audit Logging. |
ssl_verification_pre_auth | Enable SSL verification for Pre-auth/SSO metadata. |
ssl_verification_reverse_proxy | Enable SSL verification for Reverse Proxied Web Applications. |
ssl_verification_webdav | Enable SSL verification for WebDAV. |
sso_ca_aia_issuers | AIA CA issuers URL for SSO |
sso_ca_cert_pkcs_12_file | PKCS12 file containing ca certificate and ca private key.Overwrites sso_ca_certificate/sso_ca_private_key if these are also supplied |
sso_ca_cert_pkcs_12_pwd | Password protecting the ca cert/key PKCS12 file. |
sso_ca_certificate | Certificate Authority certificate for SSO |
sso_ca_crl_distribution_point | CRL distribution point URL for SSO |
sso_ca_private_key | |
sso_enabled | Enable to for SSO with external IDP |
sso_trusted_roots | Trusted roots for kerberos authentication for SSO. |
sso_trusted_roots_pkcs_12_file | PKCS12 file containing trusted roots. Overwrites sso_trusted_roots if it was also supplied |
sso_trusted_roots_pkcs_12_pwd | Password protecting the trusted roots PKCS12 file. |
trusted_ca | Domain level trusted Certificate Authorities |
twofactor | URI to a twofactor-provider. |
twofactor_trusted_browser_enabled | If enabled, users will be allowed to mark a browser as "trusted", so an MFA token is not required for the next 30 days. |
twofactor_whitelisted_labels | List with labels in the format key:value that are used toexempt users from doing MFA login. |
twofactor_whitelisted_subnets | List of IPv4 subnets that do not have to perform MFA in order to sign in to the Workspace using this domain. |
use_legacy_clipboard_implementation | Force all applications to use the legacy clipboard implementation. |
use_legacy_keyboard_implementation | Force all applications to use the legacy keyboard implementation. |
workspace_url | The Workspace base URL. This is used to construct the redirect URL for the Authentication Provider. |
partial_update
Update some details of domain. Note that the name cannot be changed on an existing domain.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this domain. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
name | Domain name to filter on. |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
admin_context_labels | List with labels in the format key:value. These can be used for context awareness. |
admin_user_labels | List with labels in the format key:value that are used todefine which users have admin credentials. |
apitoken_whitelisted_subnets | List of IPv4 subnets that can perform api calls using token authentication when enabled. |
apitoken_whitelisted_subnets_enabled | If enabled, api calls using token authentication can only be done from the whitelisted subnets. |
app_session_keepalive_timeout | Maximum time in minutes that disconnected application sessions are kept alive on the backend. Must be at least one 1 minute and at most 24 hours. Requires a manual apply changes using the Update API. |
app_session_upload_enabled | Whether or not application session are recorded. The recordings are uploaded to the remote server specified by app_session_upload_url. |
app_session_upload_url | URL of the fileserver to upload application session recordings to. Both WebDAV and SMB/CIFS fileservers are supported. For WebDAV, the URL structure is: http(s)://username:password@fqdn_or_ip/path/to/destination. For SMB/CIFS, the URL structure is smb://domain\username:password@fqdn_or_ip/share_name/path/to/destination. Recordings that cannot be uploaded will be removed after seven days. |
app_session_upload_use_domain_fqdn | If True, the domain FQDN will be used in the username when contacting the SMB/CIFS fileserver. If False, the domain netbios will be used instead. |
async_clipboard_timeout | Timeout (in seconds) to wait for responses from the client or the application server in the new async clipboard implementation. Users will need to log out and back in to apply a new timeout to their application sessions. |
auth_provider | URI to a auth-provider. Set to none if no auth-provider is configured. |
auto_sign_out_enabled | Automatically sign out users inactive for a pre-defined amount of time. |
auto_sign_out_labels | List with labels in the format key:value that are used to define for which users the auto sign out setting applies. |
auto_sign_out_timeout | Timeout (in seconds) to wait before signing out an inactive user. |
base_dn | Used to bind to the Domain Controller or LDAP Server. E.g.: dc=domain,dc=local |
bind_name | Username used for import of labels (groups and users) and application servers. It is also used to fetch a user's objectSid attribute from the DC/LDAP server when SSO is enabled. |
bind_password | Password used for import of labels (groups and users) and application servers. It is also used to fetch a user's objectSid attribute from DC/LDAP server when SSO is enabled. |
change_password_failed_msg | Set a custom password to show to user when they failed to change their password. |
change_password_failed_msg_enabled | If enabled, a message set by the admin will also be added to the api response |
create_bind_name | Advanced setting to configure the function for "Create Bind Name". |
default_host_header | |
default_keyboard_layout | Default keyboard layout for new users from this domain. |
default_locale | This language is used as fall-back when the browser of the user does not support any of the languages. |
default_polygon_enabled | Enable/disable polygon for all new users of this domain. Users can still manually enable/disable polygon from their user profile. |
default_profile_update_required | When set a profile update is required at next sign in for all new users of this domain. |
default_tours_enabled | Enable/disable guided tours for all new users of this domain. Users can still manually enable/disable guided tours from their user profile. |
dns_servers | Comma separated list of IP addresses of the DNS server(s) used to resolve hostnames connected to this domain. Is typically equal to the IP(s) of the Domain Controller(s). E.g.: 172.1.0.1,172.1.0.2 |
external_audit_basic_auth_enabled | When enabled an authorization header will be added to requests made to the external_audit_url |
external_audit_enabled | Enable to sent audit logs to external audit system |
external_audit_password | Password used when Basic Auth is enabled for external audit |
external_audit_url | The external audit URL. This is used to sent audit logs the external audit system. |
external_audit_username | Username used when Basic Auth is enabled for external audit |
find_groups | Advanced setting to configure the function for "Find Groups". |
fqdn | Used to sign in with e-mail address like user name. And for direct tcp SMB authentication. E.g. domain.local |
is_admin | When set to true, admin users of this domain are allowed to configure all domains, global settings and have access to the Dashboard. |
ldap_ssl_enabled | Is required to allow users to change their password via the Workspace. Requires SSL certificate on Domain Controller or LDAP Server. |
local_clipboard_push_max_size | Maximum size in MB of data that can be pushed to the local clipboard, per clipboard data type. Must be minimum 5 and maximum 50 MB. This setting only applies to the async clipboard implementation. |
max_licensed | The maximum number of users from this domain that can be signed in to the Workspace at the same time (concurrent users license), or the maximum number of users a domain may have (named users license).Only used when max_licensed_enabled is set to true. |
max_licensed_enabled | Whether to limit the number of users from this domain that are signed in at the same time (concurrent users license) or the maximum number of users a domain may have (named users license). |
netbios | NetBIOS name of the domain on the Domain Controller or LDAP Server. |
privacy_policy_acceptance_required | If enabled (default), each user will have to accept the Privacy Policy the first time they sign in. Disabling means that this domain is not GDPR (European General Data Protection Regulation) compliant. |
recorded_user_labels | List with labels in the format key:value that are used todefine which sessions must be recorded. |
server | One or more (comma-separated) IPv4 addresses or FQDN's of the Domain Controller or LDAP Server. E.g. ad01.domain.local |
sign_in_context_labels | List with labels in the format key:value. These can be used for context awareness. |
sign_in_user_labels | List with labels in the format key:value that are used towhitelist users to sign in when whitelisting is enabled. |
ssl_verification_external_audit | Enable SSL verification for External Audit Logging. |
ssl_verification_pre_auth | Enable SSL verification for Pre-auth/SSO metadata. |
ssl_verification_reverse_proxy | Enable SSL verification for Reverse Proxied Web Applications. |
ssl_verification_webdav | Enable SSL verification for WebDAV. |
sso_ca_aia_issuers | AIA CA issuers URL for SSO |
sso_ca_cert_pkcs_12_file | PKCS12 file containing ca certificate and ca private key.Overwrites sso_ca_certificate/sso_ca_private_key if these are also supplied |
sso_ca_cert_pkcs_12_pwd | Password protecting the ca cert/key PKCS12 file. |
sso_ca_certificate | Certificate Authority certificate for SSO |
sso_ca_crl_distribution_point | CRL distribution point URL for SSO |
sso_ca_private_key | |
sso_enabled | Enable to for SSO with external IDP |
sso_trusted_roots | Trusted roots for kerberos authentication for SSO. |
sso_trusted_roots_pkcs_12_file | PKCS12 file containing trusted roots. Overwrites sso_trusted_roots if it was also supplied |
sso_trusted_roots_pkcs_12_pwd | Password protecting the trusted roots PKCS12 file. |
trusted_ca | Domain level trusted Certificate Authorities |
twofactor | URI to a twofactor-provider. |
twofactor_trusted_browser_enabled | If enabled, users will be allowed to mark a browser as "trusted", so an MFA token is not required for the next 30 days. |
twofactor_whitelisted_labels | List with labels in the format key:value that are used toexempt users from doing MFA login. |
twofactor_whitelisted_subnets | List of IPv4 subnets that do not have to perform MFA in order to sign in to the Workspace using this domain. |
use_legacy_clipboard_implementation | Force all applications to use the legacy clipboard implementation. |
use_legacy_keyboard_implementation | Force all applications to use the legacy keyboard implementation. |
workspace_url | The Workspace base URL. This is used to construct the redirect URL for the Authentication Provider. |
delete
Delete a domain. This will also delete all information attached to this domain, such as applications, drives, users, and domain specific configuration. Deleting a domain that is currently the default domain is only possible by first setting another domain as the default domain.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this domain. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
name | Domain name to filter on. |
search |
query_ldap_appservers
Do an LDAP query to the LDAP-server for servers defined in the domain.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this domain. |
query_ldap_groups
Do an LDAP query to the LDAP-server for groups defined in the domain.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this domain. |
query_ldap_users
Do an LDAP query to the LDAP-server for users defined in the domain.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this domain. |
drives
list
List drives, which can be filtered with parameters "domain" (by ID) or "domain_name".
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | Return only files for filtered user, also for admins |
search |
create
Create a new drive.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
backend required | The protocol used for accessing the drives. Can be "CIFS" (a.k.a. SMB or Samba), "WEBDAV" or "ONEDRIVE". |
context_labels required | List with context policies in the format key:value that are assigned to this drive. These can be used for context awareness. |
config required | Configuration for this element, depending of the selected backend. See /drives/backends/ for the configurable fields. Only the value of each configuration item can be changed, and only when it is not read-only. |
description required | Free text description of the drive. |
domain required | URI to the domain this drive belongs to. |
name required | Name of the drive as it will be displayed in the Workspace, in the left-pane of the Files tab. |
unc | UNC that will be used by the application server to access the drives. This UNC path is needed when using "Open with" as action on the Files tab in the Workspace. Note that this path can be parameterized with <username> and <domain>. Example: \\FILESERVER\Home\<username>\Documents |
url required | URL of the file server that will be used by the API to communicate with the file server. Note that this path can be parameterized with <username> and <domain>. The URL format is backend specific: please refer to /drives/backends/ for examples. |
use_domain | For WEBDAV only: during authentication against the file server, it may be required to pass the domain name. Set to true if this the file server is configured that way. |
labels required | List with labels in the format key:value that are assigned to this drive. These can be used for organizational purposes. |
user_labels required | List with user labels in the format key:value that are assigned to this drive. When logging in, only users that match one of these labels will have access to this drive. |
smb_max_protocol | Maximum SMB protocol version to use. |
authentication_role | |
require_smb_signing | Require SMB signing to be enabled, so the SMB messages are always signed. |
read
Get details of a drive. A drive corresponds to a shared resource on a file server and is shown in the left column of the Files tab in the Workspace.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | Return only files for filtered user, also for admins |
search |
update
Update details of a drive.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | Return only files for filtered user, also for admins |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
backend required | The protocol used for accessing the drives. Can be "CIFS" (a.k.a. SMB or Samba), "WEBDAV" or "ONEDRIVE". |
context_labels required | List with context policies in the format key:value that are assigned to this drive. These can be used for context awareness. |
config required | Configuration for this element, depending of the selected backend. See /drives/backends/ for the configurable fields. Only the value of each configuration item can be changed, and only when it is not read-only. |
description required | Free text description of the drive. |
domain required | URI to the domain this drive belongs to. |
name required | Name of the drive as it will be displayed in the Workspace, in the left-pane of the Files tab. |
unc | UNC that will be used by the application server to access the drives. This UNC path is needed when using "Open with" as action on the Files tab in the Workspace. Note that this path can be parameterized with <username> and <domain>. Example: \\FILESERVER\Home\<username>\Documents |
url required | URL of the file server that will be used by the API to communicate with the file server. Note that this path can be parameterized with <username> and <domain>. The URL format is backend specific: please refer to /drives/backends/ for examples. |
use_domain | For WEBDAV only: during authentication against the file server, it may be required to pass the domain name. Set to true if this the file server is configured that way. |
labels required | List with labels in the format key:value that are assigned to this drive. These can be used for organizational purposes. |
user_labels required | List with user labels in the format key:value that are assigned to this drive. When logging in, only users that match one of these labels will have access to this drive. |
smb_max_protocol | Maximum SMB protocol version to use. |
authentication_role | |
require_smb_signing | Require SMB signing to be enabled, so the SMB messages are always signed. |
partial_update
Update some details of a drive.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | Return only files for filtered user, also for admins |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
backend | The protocol used for accessing the drives. Can be "CIFS" (a.k.a. SMB or Samba), "WEBDAV" or "ONEDRIVE". |
context_labels | List with context policies in the format key:value that are assigned to this drive. These can be used for context awareness. |
config | Configuration for this element, depending of the selected backend. See /drives/backends/ for the configurable fields. Only the value of each configuration item can be changed, and only when it is not read-only. |
description | Free text description of the drive. |
domain | URI to the domain this drive belongs to. |
name | Name of the drive as it will be displayed in the Workspace, in the left-pane of the Files tab. |
unc | UNC that will be used by the application server to access the drives. This UNC path is needed when using "Open with" as action on the Files tab in the Workspace. Note that this path can be parameterized with <username> and <domain>. Example: \\FILESERVER\Home\<username>\Documents |
url | URL of the file server that will be used by the API to communicate with the file server. Note that this path can be parameterized with <username> and <domain>. The URL format is backend specific: please refer to /drives/backends/ for examples. |
use_domain | For WEBDAV only: during authentication against the file server, it may be required to pass the domain name. Set to true if this the file server is configured that way. |
labels | List with labels in the format key:value that are assigned to this drive. These can be used for organizational purposes. |
user_labels | List with user labels in the format key:value that are assigned to this drive. When logging in, only users that match one of these labels will have access to this drive. |
smb_max_protocol | Maximum SMB protocol version to use. |
authentication_role | |
require_smb_signing | Require SMB signing to be enabled, so the SMB messages are always signed. |
delete
Delete a drive.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | Return only files for filtered user, also for admins |
search |
copy
Copy files and folders from this drive to the same or another drive. * source_paths: List of paths of the files and/or folders to copy. Paths are absolute w.r.t. to root of the drive. * destination_drive: URI of the destination drive. If omitted, the current drive is used. * destination_path: Path to the folder to copy the files and/or folders to. The path is absolute w.r.t. to root of the (destination) drive. Use "/" to copy to the root.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
backend required | The protocol used for accessing the drives. Can be "CIFS" (a.k.a. SMB or Samba), "WEBDAV" or "ONEDRIVE". |
context_labels required | List with context policies in the format key:value that are assigned to this drive. These can be used for context awareness. |
config required | Configuration for this element, depending of the selected backend. See /drives/backends/ for the configurable fields. Only the value of each configuration item can be changed, and only when it is not read-only. |
description required | Free text description of the drive. |
domain required | URI to the domain this drive belongs to. |
name required | Name of the drive as it will be displayed in the Workspace, in the left-pane of the Files tab. |
unc | UNC that will be used by the application server to access the drives. This UNC path is needed when using "Open with" as action on the Files tab in the Workspace. Note that this path can be parameterized with <username> and <domain>. Example: \\FILESERVER\Home\<username>\Documents |
url required | URL of the file server that will be used by the API to communicate with the file server. Note that this path can be parameterized with <username> and <domain>. The URL format is backend specific: please refer to /drives/backends/ for examples. |
use_domain | For WEBDAV only: during authentication against the file server, it may be required to pass the domain name. Set to true if this the file server is configured that way. |
labels required | List with labels in the format key:value that are assigned to this drive. These can be used for organizational purposes. |
user_labels required | List with user labels in the format key:value that are assigned to this drive. When logging in, only users that match one of these labels will have access to this drive. |
smb_max_protocol | Maximum SMB protocol version to use. |
authentication_role | |
require_smb_signing | Require SMB signing to be enabled, so the SMB messages are always signed. |
download
Download one or multiple file(s) and/or folder(s) on the given path(s). * path: Absolute path (w.r.t. the root of the drive) to download. Use "/" ("%2F") to download a complete drive. Supply multiple path arguments to download multiple combined. generate-preview: Generate a preview for the file on the given path within a drive. This will return a link which can be polled and where when completed a url will be provided on which the generated preview will be available. * path: Absolute path (w.r.t. the root of the drive) to generate a preview for. get-preview: Show the preview of the file on the given path within a drive. If the file requires a conversion (any non video/audio/image files), it first needs to be generated using generate-preview. * path: Absolute path (w.r.t. the root of the drive) to preview. * server_id: The server where the preview was generated, if a conversion was required. * guid: The guid provided by generate-preview, if a conversion is required.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
generate_preview
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
backend required | The protocol used for accessing the drives. Can be "CIFS" (a.k.a. SMB or Samba), "WEBDAV" or "ONEDRIVE". |
context_labels required | List with context policies in the format key:value that are assigned to this drive. These can be used for context awareness. |
config required | Configuration for this element, depending of the selected backend. See /drives/backends/ for the configurable fields. Only the value of each configuration item can be changed, and only when it is not read-only. |
description required | Free text description of the drive. |
domain required | URI to the domain this drive belongs to. |
name required | Name of the drive as it will be displayed in the Workspace, in the left-pane of the Files tab. |
unc | UNC that will be used by the application server to access the drives. This UNC path is needed when using "Open with" as action on the Files tab in the Workspace. Note that this path can be parameterized with <username> and <domain>. Example: \\FILESERVER\Home\<username>\Documents |
url required | URL of the file server that will be used by the API to communicate with the file server. Note that this path can be parameterized with <username> and <domain>. The URL format is backend specific: please refer to /drives/backends/ for examples. |
use_domain | For WEBDAV only: during authentication against the file server, it may be required to pass the domain name. Set to true if this the file server is configured that way. |
labels required | List with labels in the format key:value that are assigned to this drive. These can be used for organizational purposes. |
user_labels required | List with user labels in the format key:value that are assigned to this drive. When logging in, only users that match one of these labels will have access to this drive. |
smb_max_protocol | Maximum SMB protocol version to use. |
authentication_role | |
require_smb_signing | Require SMB signing to be enabled, so the SMB messages are always signed. |
move
Move files and folders from this drive to the same or another drive. Also to be used for renaming files and folders. * source_paths: List of paths of the files and/or folders to move/rename. Paths are absolute w.r.t. to root of the drive. When renaming, only one path can be provided. * destination_drive: URI of the destination drive. If omitted, the current drive is used. * destination_path: Path to the folder to move the files and/or folders to. The path is absolute w.r.t. to root of the (destination) drive. Use "/" to move to the root. To rename, the destination path ends with the new file/folder name.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
backend required | The protocol used for accessing the drives. Can be "CIFS" (a.k.a. SMB or Samba), "WEBDAV" or "ONEDRIVE". |
context_labels required | List with context policies in the format key:value that are assigned to this drive. These can be used for context awareness. |
config required | Configuration for this element, depending of the selected backend. See /drives/backends/ for the configurable fields. Only the value of each configuration item can be changed, and only when it is not read-only. |
description required | Free text description of the drive. |
domain required | URI to the domain this drive belongs to. |
name required | Name of the drive as it will be displayed in the Workspace, in the left-pane of the Files tab. |
unc | UNC that will be used by the application server to access the drives. This UNC path is needed when using "Open with" as action on the Files tab in the Workspace. Note that this path can be parameterized with <username> and <domain>. Example: \\FILESERVER\Home\<username>\Documents |
url required | URL of the file server that will be used by the API to communicate with the file server. Note that this path can be parameterized with <username> and <domain>. The URL format is backend specific: please refer to /drives/backends/ for examples. |
use_domain | For WEBDAV only: during authentication against the file server, it may be required to pass the domain name. Set to true if this the file server is configured that way. |
labels required | List with labels in the format key:value that are assigned to this drive. These can be used for organizational purposes. |
user_labels required | List with user labels in the format key:value that are assigned to this drive. When logging in, only users that match one of these labels will have access to this drive. |
smb_max_protocol | Maximum SMB protocol version to use. |
authentication_role | |
require_smb_signing | Require SMB signing to be enabled, so the SMB messages are always signed. |
upload
Get a link to upload a file to the given path (must be a folder) within a drive. When using the upload link you will also need to append &size=<bytes> * path: Absolute path (w.r.t. the root of the drive) to upload to. Use "/" ("%2F") to upload to the root of the drive.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
dirents > read
List the files and folders (dirent = directory entries) of a given path within a drive. * path: Absolute path (w.r.t. the root of the drive) to list. Use "/" ("%2F") to list the root of the drive.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
dirents > create
List the files and folders (dirent = directory entries) of a given path within a drive. * path: Absolute path (w.r.t. the root of the drive) to list. Use "/" ("%2F") to list the root of the drive.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
backend required | The protocol used for accessing the drives. Can be "CIFS" (a.k.a. SMB or Samba), "WEBDAV" or "ONEDRIVE". |
context_labels required | List with context policies in the format key:value that are assigned to this drive. These can be used for context awareness. |
config required | Configuration for this element, depending of the selected backend. See /drives/backends/ for the configurable fields. Only the value of each configuration item can be changed, and only when it is not read-only. |
description required | Free text description of the drive. |
domain required | URI to the domain this drive belongs to. |
name required | Name of the drive as it will be displayed in the Workspace, in the left-pane of the Files tab. |
unc | UNC that will be used by the application server to access the drives. This UNC path is needed when using "Open with" as action on the Files tab in the Workspace. Note that this path can be parameterized with <username> and <domain>. Example: \\FILESERVER\Home\<username>\Documents |
url required | URL of the file server that will be used by the API to communicate with the file server. Note that this path can be parameterized with <username> and <domain>. The URL format is backend specific: please refer to /drives/backends/ for examples. |
use_domain | For WEBDAV only: during authentication against the file server, it may be required to pass the domain name. Set to true if this the file server is configured that way. |
labels required | List with labels in the format key:value that are assigned to this drive. These can be used for organizational purposes. |
user_labels required | List with user labels in the format key:value that are assigned to this drive. When logging in, only users that match one of these labels will have access to this drive. |
smb_max_protocol | Maximum SMB protocol version to use. |
authentication_role | |
require_smb_signing | Require SMB signing to be enabled, so the SMB messages are always signed. |
dirents > delete
List the files and folders (dirent = directory entries) of a given path within a drive. * path: Absolute path (w.r.t. the root of the drive) to list. Use "/" ("%2F") to list the root of the drive.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
get-preview > read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this drive. |
favicons
list
List the available square logos. The square logo is used in the collapsed sidebar and as the favicon. Each square logo can be a generated polygon based on your primary branding color, or generated from an uploaded image.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
generate
Generate square logos for different dimensions and formats based on a single source image. Most common image formats are supported, like PNG (recommended size: 512 px), ICO, SVG and JPG. The uploaded image should be maximum 2MiB and should be square. The request body should be a 'multipart/form-data' encoded object (not JSON). Additionally, you need to specify the id of the domain you want to generate this favicon for as a query parameter, e.g. /api/v2/favicons/generate/?domain={domain_id} if the domain uri is /api/v2/domains/{domain_id}/.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
file required | Provide the file in the body of the request. |
read
Get the details of a square logo. The square logo is used in the collapsed sidebar and as the favicon. A square logo can be a generated polygon based on your primary branding color, or generated from an uploaded image.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this favicon. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
image > read
Get the actual image of the square logo, where the dimension, extension and state are defined through the query string. See the "image" field of a square logo object for examples. The square logo is used in the collapsed sidebar and as the favicon.
features
list
A list of all features - labels are provided in a list of 'key:value' pairs.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
display_name | Description to filter on. |
read
Get a single feature - labels are provided in a list of 'key:value' pairs.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this feature. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
display_name | Description to filter on. |
update
Update a feature by providing the complete object. Labels is the only field which will actually be updated (provide a list in short form).
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this feature. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
display_name | Description to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
user_labels required | List with labels in the format key:value that are assigned to this feature. The feature will only be activated for users that match at least one of the labels. |
context_labels required | List with context policies in the format key:value that are assigned to this feature. Only users that have a context that matches all of these labels will have access to this feature. |
partial_update
Update a feature by providing only the changes. Only the labels of a feature can be updated by providing a list in short form.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this feature. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
display_name | Description to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
user_labels | List with labels in the format key:value that are assigned to this feature. The feature will only be activated for users that match at least one of the labels. |
context_labels | List with context policies in the format key:value that are assigned to this feature. Only users that have a context that matches all of these labels will have access to this feature. |
file-types
list
List file types, which are used to link applications to files.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
extension | Extension to filter on. |
create
Create a new file type. File types are used to link applications to files.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
extension required | EG. pdf |
description | Description of the filetype. |
domain required | URI of the domain. |
icon | The URI of the icon. |
read
Get details of a file type. File types are used to link applications to files.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this file type. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
extension | Extension to filter on. |
update
Update details of a file type. File types are used to link applications to files.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this file type. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
extension | Extension to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
extension required | EG. pdf |
description | Description of the filetype. |
domain required | URI of the domain. |
icon | The URI of the icon. |
partial_update
Update some details of a file type. File types are used to link applications to files.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this file type. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
extension | Extension to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
extension | EG. pdf |
description | Description of the filetype. |
domain | URI of the domain. |
icon | The URI of the icon. |
delete
Delete a file type. File types are used to link applications to files. Deleting a file type will not delete the applications/files linked to it.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this file type. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
extension | Extension to filter on. |
frontend-logger
get-certificate-content
guided-tours
list
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
user | User id to filter on. |
read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this guided tour. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this guided tour. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
is_enabled | Whether this individual tour is enabled. |
partial_update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this guided tour. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
is_enabled | Whether this individual tour is enabled. |
hostheaders
list
List host headers.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
domain_name | Domain name to filter on. |
create
Add a host header to a domain.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
domain required | |
name required | Name of host header, matching the value of the HTTP Host header. |
read
Get details of a host header.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this host header. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
update
Change the details of a host header.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this host header. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
domain required | |
name required | Name of host header, matching the value of the HTTP Host header. |
partial_update
Change some details of a host header.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this host header. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
domain | |
name | Name of host header, matching the value of the HTTP Host header. |
delete
Remove a host header.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this host header. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
indexer
create
Launch a query to the indexer containing the auditing logs.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
domain | Domain URI to query information from |
query_name required | Name of query to execute (anomalies, application_concurrent_sessions, application_named_users, application_sessions, application_usage, application_usage_histogram, browser, file_accesses, os, share_accesses, shared_application_sessions, shared_application_sessions_settings, user_sessions, web_application_sessions) |
query_filter required | Query filter to run against subset, for example: "*" for all results or "app_key:"da13bd02-2f63-4d39-ab05-eb913642de81"" to get only the results for a specific app |
timestamp_from required | Timestamp to search from, in ISO 8601 format |
timestamp_to required | Timestamp to search to, in ISO 8601 format |
size | The maximum number of results to look up |
advanced |
fields
Get the list of available fields for an advanced query
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
query_name required | Name of query to execute (anomalies, application_concurrent_sessions, application_named_users, application_sessions, application_usage, application_usage_histogram, browser, file_accesses, os, share_accesses, shared_application_sessions, shared_application_sessions_settings, user_sessions, web_application_sessions) |
indexer-ingest
key-combos
list
List on-screen keyboard shortcut.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
app | App id to filter on. |
domain_name | Domain name of app to filter on. |
search |
create
Add a new on-screen keyboard shortcut to an application.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
app required | The id of the application. |
order required | The order of this key combination in the list. The key combinations will be sorted by the value of this field. There can be gaps between the values of the order fields, and it can also be negative. |
name required | Name for this key combination, will be displayed to the user. |
value required | Key combination to be sent to the app. Must be a number of existing keys joined by "+", for example "ctrl+shift+v". |
read
Get details of an on-screen keyboard shortcut.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this key combo. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
app | App id to filter on. |
domain_name | Domain name of app to filter on. |
search |
update
Update details of an on-screen keyboard shortcut.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this key combo. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
app | App id to filter on. |
domain_name | Domain name of app to filter on. |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
app required | The id of the application. |
order required | The order of this key combination in the list. The key combinations will be sorted by the value of this field. There can be gaps between the values of the order fields, and it can also be negative. |
name required | Name for this key combination, will be displayed to the user. |
value required | Key combination to be sent to the app. Must be a number of existing keys joined by "+", for example "ctrl+shift+v". |
partial_update
Update some details of an on-screen keyboard shortcut.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this key combo. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
app | App id to filter on. |
domain_name | Domain name of app to filter on. |
search |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
app | The id of the application. |
order | The order of this key combination in the list. The key combinations will be sorted by the value of this field. There can be gaps between the values of the order fields, and it can also be negative. |
name | Name for this key combination, will be displayed to the user. |
value | Key combination to be sent to the app. Must be a number of existing keys joined by "+", for example "ctrl+shift+v". |
delete
Remove an on-screen keyboard shortcut.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this key combo. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
app | App id to filter on. |
domain_name | Domain name of app to filter on. |
search |
labels
list
List all labels.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search | |
user_labels | |
context_labels |
create
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
domain required | |
key required | The key of the label |
value | The value that corresponds to the key of the label |
type |
read
Get details of a specific label.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this label. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search | |
user_labels | |
context_labels |
update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this label. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search | |
user_labels | |
context_labels |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
domain required | |
key required | The key of the label |
value | The value that corresponds to the key of the label |
type |
partial_update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this label. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search | |
user_labels | |
context_labels |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
domain | |
key | The key of the label |
value | The value that corresponds to the key of the label |
type |
delete
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this label. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
search | |
user_labels | |
context_labels |
resource-changes
list
List resource changes.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
ordering | Which field to use when ordering the results. |
action | Action to filter on. |
domain_name | Case insensitive domain name filter. |
resource_id | Case insensitive resource id filter. |
resource_type | Case insensitive resource type filter. |
timestamp | |
timestamp_to | Date time filter (format: YYYY-MM-DD HH:MM). Can be combined with timestamp_from. |
username | Case insenstive username filter. |
authentication | Case insenstive authentication filter. |
date | Date filter (format:YYYY-MM-DD). |
timestamp_from | Date time filter (format: YYYY-MM-DD HH:MM). Can be combined with timestamp_to. |
read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this resource change. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
ordering | Which field to use when ordering the results. |
action | Action to filter on. |
domain_name | Case insensitive domain name filter. |
resource_id | Case insensitive resource id filter. |
resource_type | Case insensitive resource type filter. |
timestamp | |
timestamp_to | Date time filter (format: YYYY-MM-DD HH:MM). Can be combined with timestamp_from. |
username | Case insenstive username filter. |
authentication | Case insenstive authentication filter. |
date | Date filter (format:YYYY-MM-DD). |
timestamp_from | Date time filter (format: YYYY-MM-DD HH:MM). Can be combined with timestamp_to. |
resources
list
Internal API to get the number of cpu cores and amount of memory on this appliance. This is used to check if the requirements are met during service management changes.
seal-providers
list
List seal providers.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
key | Key to filter on. |
read
Get details for a seal provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this seal provider. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
key | Key to filter on. |
update
Update details for a seal provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this seal provider. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
key | Key to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
config required | Configuration for this authentication provider. Only the value of each configuration item can be changed, and only when it is not read-only. |
partial_update
Update details for a seal provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this seal provider. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
key | Key to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
config | Configuration for this authentication provider. Only the value of each configuration item can be changed, and only when it is not read-only. |
sessions
list
List of sessions. A session corresponds with a login on the Workspace. Super admin can see all sessions, domain admin all sessions connected to his domain, a user only his own session.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
create
Create a session to login.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
username required | Username of the user. For authentication (POST): both the username and the UPN can be used. When reading (GET), the non-UPN username is returned, prefixed with the NetBIOS domain name. |
privacy_policy_accepted | True when user accepts the Privacy Policy. |
domain | The applicable domain. When not providing this field when authenticating (POST), the default domain is used. |
fingerprint | A unique value identifying a single browser/device combination. Is automatically set by the client. |
is_trusted | Mark the current browser as "trusted", no MFA token will be required for 30 days. |
new_password | Change the LDAP password of the user to this new password. To change it (POST), the fields "twofactor" (if applicable and when not being signed in) and "password" should be provided. |
password | Current LDAP password of the user needed for authentication (POST). |
twofactor | When MFA (multi-factor authentication) is required during authentication (POST), you need to provide a JSON object with following fields (depending of the type of MFA): method (e.g. phone, push) and otp (token). The available methods are provided in the response of an authentication attempt without twofactor field. |
login_without_admin_rights | |
force_mfa_login | |
logout_other_sessions |
disable_token
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
password required |
generate_token
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
password required |
heartbeat
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
last_activity required |
read
Get details of a session. A session corresponds with a login on the Workspace.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required |
delete
Delete a session to logout.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required |
shares
list
List all shares, which can be filtered with the parameter "user" (by ID).
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
access_rights | Access rights to filter on. |
user | User id to filter on. |
is_expired |
create
Create a new share. During the creation, the content of the file or folder will be fetched from the file server and stored on the Workspace as long as it does not expire. When the original file or folder is modified,the share won't be updated automatically.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
description | Free text description of the share. |
expires required | ISO time stamp when the share expires. |
mode | Can be PREVIEW (which results in a PDF) or DOWNLOAD (to share the original files and/or folders). Note that folders and multi-file shares can only be set to DOWNLOAD and will result in a ZIP file. |
name | Name of the share. Typically, the file name is used for this. |
drive required | |
paths required | Paths to the original files and/or folders (relative to the root of the drive). |
password | Optional password required to access share. |
access_rights | Can be DOMAIN (accessible to users in the same domain), EXTERNAL (accessible to everyone, even not logged-in users) or USERS (accessible to specific users or groups, as specified by the access_labels field. |
access_labels | List with labels in the format key:value that are assigned to this share. The key must be one of username or group to specify respectively usernames and group names that are allowed to access this share when access_rights is set to USERS. |
read
Get details of a share, which is a shared file of folder within a drive.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this share. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
access_rights | Access rights to filter on. |
user | User id to filter on. |
is_expired |
update
Update the detail of a share.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this share. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
access_rights | Access rights to filter on. |
user | User id to filter on. |
is_expired |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
description | Free text description of the share. |
expires required | ISO time stamp when the share expires. |
mode | Can be PREVIEW (which results in a PDF) or DOWNLOAD (to share the original files and/or folders). Note that folders and multi-file shares can only be set to DOWNLOAD and will result in a ZIP file. |
name | Name of the share. Typically, the file name is used for this. |
drive required | |
paths required | Paths to the original files and/or folders (relative to the root of the drive). |
password | Optional password required to access share. |
access_rights | Can be DOMAIN (accessible to users in the same domain), EXTERNAL (accessible to everyone, even not logged-in users) or USERS (accessible to specific users or groups, as specified by the access_labels field. |
access_labels | List with labels in the format key:value that are assigned to this share. The key must be one of username or group to specify respectively usernames and group names that are allowed to access this share when access_rights is set to USERS. |
partial_update
Update some details of a share.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this share. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
access_rights | Access rights to filter on. |
user | User id to filter on. |
is_expired |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
description | Free text description of the share. |
expires | ISO time stamp when the share expires. |
mode | Can be PREVIEW (which results in a PDF) or DOWNLOAD (to share the original files and/or folders). Note that folders and multi-file shares can only be set to DOWNLOAD and will result in a ZIP file. |
name | Name of the share. Typically, the file name is used for this. |
drive | |
paths | Paths to the original files and/or folders (relative to the root of the drive). |
password | Optional password required to access share. |
access_rights | Can be DOMAIN (accessible to users in the same domain), EXTERNAL (accessible to everyone, even not logged-in users) or USERS (accessible to specific users or groups, as specified by the access_labels field. |
access_labels | List with labels in the format key:value that are assigned to this share. The key must be one of username or group to specify respectively usernames and group names that are allowed to access this share when access_rights is set to USERS. |
delete
Delete a share. The original file or folder will be untouched.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this share. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
access_rights | Access rights to filter on. |
user | User id to filter on. |
is_expired |
update_share
Fetch the content of the file or folder again from the file server.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this share. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
description | Free text description of the share. |
expires required | ISO time stamp when the share expires. |
mode | Can be PREVIEW (which results in a PDF) or DOWNLOAD (to share the original files and/or folders). Note that folders and multi-file shares can only be set to DOWNLOAD and will result in a ZIP file. |
name | Name of the share. Typically, the file name is used for this. |
drive required | |
paths required | Paths to the original files and/or folders (relative to the root of the drive). |
password | Optional password required to access share. |
access_rights | Can be DOMAIN (accessible to users in the same domain), EXTERNAL (accessible to everyone, even not logged-in users) or USERS (accessible to specific users or groups, as specified by the access_labels field. |
access_labels | List with labels in the format key:value that are assigned to this share. The key must be one of username or group to specify respectively usernames and group names that are allowed to access this share when access_rights is set to USERS. |
ssl-offloader-certificates
list
List certificates.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
create
Create a new certificate either by generating one automatically using Let's Encrypt (is_automatic=true) or using a manually specified certificate chain and private key (is_automatic=false). Triggers a limited apply changes on the proxy service.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
certificate | SSL certificate chain in PEM format. Should include any intermediate certificates in the chain. Only allowed when is_automatic is false. |
pkcs_12_password | Password protecting the PKCS12 file. |
pkcs_12_file | PKCS12 file containing certificate and private key. |
private_key | RSA private key in PEM format. Only allowed when is_automatic is false. |
subject_names | List of FQDNs, used to generate a new certificate when creating a certificate (only allowed when is_automatic is true), or to view the subject names the certificate applies to when viewing the certificate. |
is_automatic required | Whether or not this is an automatically generated certificate. If set to true, a new certificate will be generated based on subject_names, using Let's Encrypt. By using it, you are accepting their terms and conditions (https://letsencrypt.org). Your appliance needs permanent network access to and from their servers. If set to false, certificate and private_key will be used. |
read
Get details of a certificate.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this certificate. |
delete
Remove a certificate. Triggers a limited apply changes on the proxy service.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this certificate. |
status
list
Lists appliance, service and process status and an aggregated status of the Workspace.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
tasks
read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique value identifying this task. |
twofactor-providers
list
List MFA (multi-factor authentication) providers.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
domain_name | Domain name to filter on. |
key | Key to filter on. |
domain | Domain id to filter on. |
read
Get details for an MFA (multi-factor authentication) provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
key | Key to filter on. |
domain | Domain id to filter on. |
update
Update details for an MFA (multi-factor authentication) provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
key | Key to filter on. |
domain | Domain id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
config required | Configuration for this MFA provider. Only the value of each configuration item can be changed, and only when it is not read-only. |
partial_update
Update details for an MFA (multi-factor authentication) provider.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain_name | Domain name to filter on. |
key | Key to filter on. |
domain | Domain id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
config | Configuration for this MFA provider. Only the value of each configuration item can be changed, and only when it is not read-only. |
update-outputs
list
List the output logs of an update (install, upgrade, apply changes).
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
update | Update id to filter on. |
read
Get the output log of an update (install, upgrade, apply changes).
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this output. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
update | Update id to filter on. |
updates
list
List updates (install, update, apply changes). Add the filter '?unfinished=1' to only get updates that did not finish yet or that failed without a successful retry.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
create
Apply all changes (when no version or the current version is supplied), or upgrade to a different version.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
version required | |
eula_accepted |
install
Install.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
config required | Configuration for the installation. See our documentation portal for more information. |
version_number |
read
Get details of an update.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this update. |
delete
Only used in the installer. When the installation fails, the update is deleted in order to reset the installer to its initial state.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this update. |
install-upload-backup > create
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
backup required | |
password |
user-apps
list
List user applications. List applications linked to users. At each login, the applications for a user are defined based on the user labels (groups, OUs, username etc.).
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | User id to filter on. |
favorite | Favorite state to filter on. |
read
Get details for a user application.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user app. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | User id to filter on. |
favorite | Favorite state to filter on. |
update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user app. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | User id to filter on. |
favorite | Favorite state to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
favorite | Whether or not this application is marked as favorite. |
partial_update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user app. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
user | User id to filter on. |
favorite | Favorite state to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
favorite | Whether or not this application is marked as favorite. |
user-count
list
Get the name (unique) user count per month. Each entry's date is the first day of the month.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
date | Filter for a given date in YYYY-MM-DD format. |
date__gte | Filter for dates later or equal than the given date in YYYY-MM-DD format. Can be combined with date__lte. |
date__lte | Filter for dates sooner or equal than the given date in YYYY-MM-DD format. Can be combined with date__gte. |
user-file-types
list
List file types, which are used to link applications to files.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
user | User id to filter on. |
create
Create a new file type. File types are used to link applications to files.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
file_type required | |
default_app required |
read
Get details of a file type. File types are used to link applications to files.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user file type. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
update
Update details of a file type. File types are used to link applications to files.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user file type. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
file_type required | |
default_app required |
partial_update
Update some details of a file type. File types are used to link applications to files.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user file type. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
file_type | |
default_app |
delete
Delete a file type. File types are used to link applications to files. Deleting a file type will not delete the applications/files linked to it.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user file type. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
user-profiles
list
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
user | User id to filter on. |
read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user profile. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user profile. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
default_polygon_enabled | |
keyboard_layout required | The Windows keyboard layout code of the keyboard layout to use in streamed applications. |
locale required | The two letter ISO language code of the language to use in the Workspace. |
tours_enabled required | Whether or not guided tours are enabled for this user. When reenabling tours here, all tours will be reset and shown again. |
update_required |
partial_update
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user profile. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
user | User id to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
default_polygon_enabled | |
keyboard_layout | The Windows keyboard layout code of the keyboard layout to use in streamed applications. |
locale | The two letter ISO language code of the language to use in the Workspace. |
tours_enabled | Whether or not guided tours are enabled for this user. When reenabling tours here, all tours will be reset and shown again. |
update_required |
revoke_privacy_policy
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user profile. |
user-sessions
list
List of active sessions. A session corresponds with a login on the Workspace. Super admin can see all sessions, domain admin all sessions connected to his domain.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
status | Filter on the status, which can be ACTIVE, DISCONNECTED or CLOSED. |
start | Filter the sessions started after the given time in ISO 8601 notation, e.g. 2017-12-20T23:56:12 |
end | Filter the sessions ended before the given time in ISO 8601 notation, e.g. 2017-12-20T23:56:12 |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
read
Get time and location details of a session. A session corresponds with a login on the Workspace.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
public_session_id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
status | Filter on the status, which can be ACTIVE, DISCONNECTED or CLOSED. |
start | Filter the sessions started after the given time in ISO 8601 notation, e.g. 2017-12-20T23:56:12 |
end | Filter the sessions ended before the given time in ISO 8601 notation, e.g. 2017-12-20T23:56:12 |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
update
Update the status of a session. A session corresponds with a login on the workspace.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
public_session_id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
status | Filter on the status, which can be ACTIVE, DISCONNECTED or CLOSED. |
start | Filter the sessions started after the given time in ISO 8601 notation, e.g. 2017-12-20T23:56:12 |
end | Filter the sessions ended before the given time in ISO 8601 notation, e.g. 2017-12-20T23:56:12 |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
status required | An active session can be set to CLOSED. |
partial_update
Update the status of a session. A session corresponds with a login on the Workspace.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
public_session_id required |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
status | Filter on the status, which can be ACTIVE, DISCONNECTED or CLOSED. |
start | Filter the sessions started after the given time in ISO 8601 notation, e.g. 2017-12-20T23:56:12 |
end | Filter the sessions ended before the given time in ISO 8601 notation, e.g. 2017-12-20T23:56:12 |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
status | An active session can be set to CLOSED. |
users
list
List users. LDAP/AD users are only added when they sign-in for the first time.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
username | Username to filter on. |
search | |
ordering | Which field to use when ordering the results. |
query
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
query required |
read
Get details of a user.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
username | Username to filter on. |
search | |
ordering | Which field to use when ordering the results. |
delete
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
domain | Domain id to filter on. |
domain_name | Domain name to filter on. |
username | Username to filter on. |
search | |
ordering | Which field to use when ordering the results. |
otp_reset
Reset the builtin OTP token and counter of the user.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user. |
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
date_joined | |
email | |
is_active | Designates whether this user should be treated as active. Unselect this instead of deleting accounts. |
is_superuser | Designates that this user has all permissions without explicitly assigning them. |
last_login | |
username required | Required. 150 characters or fewer. Letters, digits and @/./+/-/_ only. |
get-rdp-gateway > read
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user. |
recent-files > read
Returns the files recently opened from the Files page.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this user. |
validators
list
Lists the available validator methods.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
database
Validate database connection string, connectivity, availibility & permissions.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
database_protocol required | Database protocol: mssql or postgresql. |
database_username required | Database connection username. |
database_password required | Database connection password. |
database_name required | Database name. |
database_host required | Database hostname or IP. |
database_instance | Optional. Database instance name. Only for Microsoft SQL Server. |
database_port | Optional. Database port number. Not used when used with a named instance name. |
dns
Validate dns resolving.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
servers required | JSON list of IP addresses of DNS servers |
hostname
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
hostname required | Hostname of the appliance |
ntp_server
Validate ntp availibility.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
servers required | JSON list of IP addresses or FQDNs of NTP servers |
repo_server
Validate connectivity to a repo server.
Request Body
The request body should be a "application/json"
encoded object, containing the following items.
Parameter | Description |
---|---|
repo_server required | URL to the repo server. |
http_proxy | URL to the HTTP proxy server (if any), in the format http(s)://(username:password@)server:port |
versions
list
Lists all known versions. If the repo server can be reached version details are updated.
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
limit | Number of results to return per page. |
offset | The initial index from which to return the results. |
number |
read
Get the details of a version.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this version. |
Query Parameters
The following parameters can be included as part of a URL query string. Filters can be combined to further narrow the results.
Parameter | Description |
---|---|
number |
download
Download the packages for this version so upgrading to this version is faster. This does not result in any service interruption, but you cannot upgrade or download other versions while a version is being downloaded.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this version. |
license_terms
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this version. |
allowed-upgrade-versions > read
For a given version, lists all details to which an upgrade is possible.
Path Parameters
The following parameters should be included in the URL path.
Parameter | Description |
---|---|
id required | A unique integer value identifying this version. |