Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}
{{product.name}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Users / Update

  • Article
  • 2 minutes to read

Operation Information

Creates a User within Tenable.io.

This is a Premium Integration.

Authentication

This operation requires authentication, the details of which can be securely stored on your instance in a KeySafe Key of type Tenable.

To create a key of this type:

  • In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
  • Click on the + Create New Key button;
  • On the resulting Create New Key form, choose Tenable in the Type pick list;
  • Give the Tenable KeySafe key a Title (this is the name / identifier for the Tenable account as you will see it when using the cloud automation node in your workflows);
  • Optionally populate the Description field;
  • Populate the following fields accordingly, then click the Create Key button to create your new key:
Name Type Description
API Access Key string The Tenable API Access Key
Secret Key string The Tenable Secret Key

Revoking Access

If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just delete the relevant KeySafe key(s) from the KeySafe list.

Warning

This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked Tenable account, so you will need to manage these workflows accordingly.

Input Parameters

Display Name ID Type Description Required Supported Values
User ID userID string None provided Yes None provided
Username username string The login name for the user. A valid username must be in the format, name@domain, where domain corresponds to a domain approved for your Tenable.io instance. No None provided
Password password string The initial password for the user. Passwords must be at least 12 characters long and contain at least one uppercase letter, one lowercase letter, one number, and one special character symbol. No None provided
Permissions permissions string Permissions for the User Yes Basic, Scan Operator, Standard, Scan Manager, Administrator
Name name string The name of the user (for example, first and last name). No None provided
Email email string The email address of the user. A valid email address must be in the format, name@domain, where domain corresponds to a domain approved for your Tenable.io instance. This email address overrides the email address set in username. If your request omits this parameter, Tenable.io uses the username value as the user’s email address. No None provided

Output Parameters

Display Name ID Type Description
Error Message error string Any errors returned by the Freshstatus API
Status Code status string The status of the operation: ok / failed
User ID id string The ID of the User
Username userName string The username of the User
Name of the User name string The name of the User
User Email email string The email of the User
User Type type string None provided
User Aggregate aggregate string None provided
User Enabled enabled string None provided
  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document