Tenants and Channels
Tenants vs. Channels
Tenants are organizational units. Administrator user accounts are provisioned within these tenants. Once provisioned, users can view protected sites, attack heuristics, real-time data, and other configuration information.
Alternatively, you can have your ThreatX platform organized by channels, where a channel can contain multiple tenants. If you have channels, you can administer all users and sites within the tenants and add tenants as needed. See: Channels
Customers
List Customers
Parameters | Type |
---|---|
|
String |
|
String |
$ curl api.threatx.com/tx_api/v2/customers \
--header 'Content-Type: application/json' \
--data @- <<EOF
{
"command": "list",
"token": "<access_token>"
}
EOF
Replace <access_token>
with your access token from the last command.
{
"Ok": [
{
"name": "testco",
"contact_email": "alice@testco.com",
"description": "Tesco tenant",
"active": true,
"autoblock_threshold": 70,
"autoblock_timeout": 3600,
"block_embargo": true,
"ssl_ciphers": null,
"notify_threshold": 100,
"sso": null,
"allow_super_admin_users": true,
"allow_channel_admin_users": true,
"tenant_admin_default": null,
"uuid": "<tenant_uuid>"
}
]
}
Update Customer
The SSO object is used to configure the SSO parameters. All other parameters to the customer object should not be modified when configuring SSO.
Parameters | Type |
---|---|
|
String |
|
String |
|
String |
|
CustomerObject |
Parameters | Type |
---|---|
|
String |
|
String |
|
String |
|
Boolean |
|
Integer |
|
Integer |
|
SSO Object |
Parameters | Type | Description |
---|---|---|
|
Boolean |
When true, users belonging to the tenant are allowed to sign in to the ThreatX user interface using SSO. |
|
Boolean |
When true, users are required to use SSO to sign in to the ThreatX user interface. |
|
String |
IDP metadata URL or file. See the Prerequisites. |
$ curl api.threatx.com/tx_api/v2/customers \
--header 'Content-Type: application/json' \
--data @- <<EOF
{
"command": "update",
"token": "<login_token>",
"name": "testco",
"customer": {
"name": "testco",
"contact_email": "alice@testco.com",
"description": "Testco tenant",
"active": true,
"autoblock_threshold": 70,
"autoblock_timeout": 3600,
"block_embargo": true,
"ssl_ciphers": null,
"notify_threshold": 100,
"allow_super_admin_users": true,
"allow_channel_admin_users": true,
"tenant_admin_default": null,
"sso": {
"enabled": true,
"required": false,
"saml_metadata_url": "https://login.microsoftonline.com/daad3805-fde6-4334-817f-82c723533123/federationmetadata/2007-06/federationmetadata.xml"
}
}
}
EOF
{ "Ok": "testco updated." }
Channels
List Channels
Parameters | Type |
---|---|
|
String |
|
String |
$ curl api.threatx.com/tx_api/v2/channels \
-H 'Content-Type: application/json' \
--data @- <<EOF
{
"command": "list",
"token":" "<access_token>"
}
EOF
{
"Ok": [
{
"name": "test_channel",
"require_totp_setup": null,
"uuid": "81815E73-ABB9-4533-977B-93964B8AAB73",
"sso": null
}
]
}
Update Channels using the API
The update
command updates a specified channel.
|
Type |
|
String |
|
String |
|
Parameter | Type |
---|---|
|
String |
|
Name | Type | Description |
---|---|---|
|
Boolean |
When true, users belonging to the channel are allowed to sign in to the ThreatX user interface using SSO. |
|
Boolean |
When true, users in the channel are required to use SSO to sign in to the ThreatX user interface. |
|
String |
IDP metadata URL or file. See the Prerequisites. |
$ curl {url-txapi}/channels \
--header 'Content-Type: application/json' \
--data @- <<EOF
{
"command": "update",
"token": "<login_token>",
"channel": {
"name": "test_channel",
"sso": {
"enabled": true,
"required": false,
"saml_metadata_url": "https://login.microsoftonline.com/daad3805-fde6-4334-817f-82c723533123/federationmetadata/2007-06/federationmetadata.xml"
}
}
}
EOF
{"Ok": "Channel: test_channel updated."}