Fetch Okta Token

Category: Multi-factor AuthenticationPackage: TruBot.MultiFactorAuthentication.Activities

Purpose

Generates security token for two-way authentication process.

Description

The Fetch Okta Token component generates security token that is used in the second round of a two-way authentication process. In the example below, the Fetch Okta Token activity is configured for accessing a google account.

Note

In a typical two-way authentication scenario, the token is generated by using an Authenticator app and is manually provided as input by the user when the two-way authentication prompt appears.

Automating two-way authentication is not advisable in production environments as it undermines the purpose of having some form of human involvement in the authentication process. See Disclaimer.

A 'Fetch Okta Token' activity configuration

A workflow to sign-in to a Google account generated by
recording user actions. The 'Fetch Okta Token' is added later in the workflow.

In the above workflow, the manually entered token value has been replaced with the token variable generated from the 'Fetch Okta Token' activity.

A 'Fetch Okta Token' activity configuration

Properties

Property	Data Type	Description
General
Display Name	String	Display name of the component..
Enable Pause	-NA-	Option to pause the activity (related to the component) during a job execution after receiving a pause control signal from the Cockpit application. The checkbox is selected by default.
Input
Secret Key*	SecurString	Secret key that is used for generating for token. How to access secret key?
Misc
Enable Bookmark	-NA-	Option to set a bookmark.
Is Reserved	-NA-	Option to disable data tracing related to the component.
Output
Token*	String	A number generated using an algorithm that is valid for 30 seconds since the time of its generation.
Note: Fields marked with * sign are mandatory.

Disclaimer

Automating two-way authentication using Multi-factor authentication activities enhances the TruBot's capabilities but it is not recommended to use these activities directly in production environments. Bots should have dedicated accounts with appropriate security measures in place to ensure the integrity of sensitive data and operations.