Thycotic - Suspend User
- 22 Sep 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Thycotic - Suspend User
- Updated on 22 Sep 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Thycotic - Suspend User disables a user in Thycotic for:
- Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
Note:
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
General Settings
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
Use stored credentials from Thycotic - Select this option to use the first Thycotic Secret Server connected adapter credentials. Thycotic
- When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
Required Fields
These fields are required to run the Enforcement Action.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Connection and Credentials
When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.
- Thycotic Secret Server URL - The full URL of the Thycotic Secret Server.
- For on-prem Thycotic Secret Server, needs to be in the following format: https://<hostname>/SecretServer (e.g. https://demo-server/SecretServer)
- For cloud Thycotic Secret Server, needs to be in the following format: https://<tenant>.secretservercloud.com (e.g https://mycompany.secretservercloud.com)
- User Name and Password - The credentials of a local Thycotic user that has the Required Permissions to fetch assets.
- Port - The port used for the connection.
- Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
- HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
- HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
- HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?