The display name of the node within the flows.

System-wide unique ID of the plugin instance.

Configuration option determining the type of operation to perform:

• Add User to Group: Adds a user to a group.
• Find Groups: Retrieves groups based on the criteria.
• Get Group: Retrieves details on the specified group.
• Remove User from Group: Removes a user from a group.

Successful results for an action are placed in msg.payload.okta.[uniqueId].response.

Retrieves groups according to the Search Type. When Search Type is No Filtering (List Groups), the node lists groups returning up to Size Limit groups. When Search Type is Query, the node searches the groups’ profile.name property finding those that start with the specified Group Query value. When Search Type is Filter, the node filters groups against a subset of properties using the specified Group Query value. When Search Type is Search, the node searches for groups using a larger set of available properties.

See the Okta List Groups REST API for details on constructing a Filter or Search template. The Group Query supports using mustache variable substitution from the incoming message. Visit the Template Engine and Formatters page to learn more.

The Expand Response configuration determines what additional information to include in found groups. Possible values are app, stats, or app,stats. Any other value will cause a failure.

The maximum number of groups to return from a find action.

The group being retrieved or having a user added or removed. If the Group ID is set to Standard Group ID Location, the group ID is obtained within the standard response location at group.id. The location is set by a successful Get Group or Find Groups action.

The user being added or removed from a group. If the User ID is set to Standard User ID Location, the user ID is obtained within the standard response location at user.id. The location is set by a successful Get User or Find Users action in the NL-Okta-Users node. The User ID may also be the user’s login ID.

The display name of the node within the flows.

A system-wide unique identifier for this plugin instance used to locate the service.

The Path Segment defines a mustache template for the URL’s path after the version. The following example sets the path for setting a user’s status to SUSPENDED. The path for suspending a user with a str context value is users/{{payload.userId}}/lifecycle/suspend. If the payload.userId is 01234567890, the final URL is https://[okta-server]/api/v1/users/01234567890/lifecycle/suspend, where okta-server comes from the plugin instance configuration.

The HTTP Method must evaluate to one of GET, POST, PUT, PATCH, or DELETE. Any other value will cause a non-recoverable failure.

When needed, the Query Parameters must evaluate to a JSON object or string. When Query Parameters evaluates to an object, the object contains the query parameters (URL parameters) as key-value pairs. Values may include any value convertible to a string. Array values will result in the same key being supplied with each element as a value within the query parameters. When Query Parameters evaluates to a string, it must contain the URL parameters in the key1=value1&key2=value2&...&keyN=valueN format. If the Query Parameters uses the {} JSON context, mustache template substitution is applied prior to generation of the final JSON object.

When needed, the Body Parameters must evaluate to a JSON object. The object contains the request payload as specified by the REST API end-point. If the Body Parameters uses the {} JSON context, mustache template substitution is applied prior to generation of the final JSON object.

The display name of the node within the flows.

A system-wide unique identifier for this plugin instance used to locate the service.

Configuration option determining the type of operation to perform:

• Find Users: Retrieve users based on the criteria.
• Get User: Retrieves a user using an ID number or login ID.
• Get User Groups: Retrieves the groups a user is a member of.
• Create User: Creates a new user.
• Update User: Updates an existing user.
• Activate User: Activates a user.
• Deactivate User: Deactivates a user.
• Delete User: Deletes a user.
• Expire User Password: Expires a user’s password.
• Reactivate User: Reactivates a user.
• Suspend User: Suspends a user.
• Unsuspend User: Undoes a user suspension.

Successful results for an action are placed in msg.payload.okta.[uniqueId].response.

Search operation used to find users. When Search Type is No Filtering (List Users), the node lists users returning up to Size Limit users. When Search Type is Query, the node searches existing the users’ profile.firstName, profile.lastName, and profile.email properties finding those that start with the specified User Query value. When Search Type is Filter, the node filters users against a subset of properties using the specified User Query value. The supported filter properties are status, lastUpdated, id, profile.login, profile.firstName, profile.lastName, and profile.email properties. When Search Type is Search, the node searches for users using the specified User Query value.

The query configuration used by the selected Search Type. The User Query supports using mustache variable substitution from the incoming message. See the Okta List Users REST API for details on constructing a Filter or Search template. Visit the Template Engine and Formatters page to learn more.

If specified, the Sort By fields indicates the property to sort the results by. The Sort Order is always applied.

Sorts results in ascending or descending order.

The maximum number of users to return for a find action.

The user affected by the current action. If the User ID is set to Standard User ID Location, the user ID is obtained within the standard response location at user.id. The location is set by a successful Find Users action. The User ID may also be the user’s login ID.

The Create JSON Payload is used to define the initial settings of a new user. See Okta API v1 Create User page for detailed documentation on the structure of the JSON payload. The sample payload illustrates how to create a user with a few values defined dynamically using mustache variable substitution from the incoming message. Visit the Template Engine and Formatters page to learn more.

The Update JSON Payload is used to define the update settings. See Okta API v1 Update User page for detailed documentation on the structure of the JSON payload. The sample payload illustrates how to update a user with a few values defined dynamically using mustache variable substitution from the incoming message. Visit the Template Engine and Formatters page to learn more.

This flag is used when expiring a user’s password. If Temp Password evaluates to a JavaScript truthy value, the user is assigned a temporary password, which is returned in tempPassword.

The display name of the node within the flows.

A system-wide unique identifier for this plugin instance used to locate the service.

Configuration option determining the type of operation to perform:

• List User Types: Retrieves the list of user types defined within the Okta service.

Successful results for an action are placed in msg.payload.okta.[uniqueId].response.