Jump to a Section

Events

  • User Added to Application Membership - Beta

    Okta - User Added to Application Membership webhook event. Listen for the event triggered in Okta, that will trigger the FLO in real time.

    Note - The Okta webhooks are currently in beta.

    Important: Okta webhooks will only trigger one registered endpoint for any given event type, meaning if you have multiple FLOs and/or other event hook endpoints configured for one specific event type, Okta will only send a request to one of those endpoints. It is recommended that you only activate one endpoint per event type, otherwise all endpoints will not receive event notifications.

    Instructions

    1. In order to create an Okta Webhook, you will first need an accessible URL endpoint before configuring the Webhook in Okta. This can be done by creating a FLO using this webhook event, and then saving the FLO. Turn on the FLO (important). Click the ‘Webhook settings’ button at the bottom right of this card. This will present you with the Webhook URL. Copy the URL. Webhook Settings
    2. Provide the URL when configuring your Okta Webhook. Additionally, you must provide the event type: application.user_membership.add.
    3. Once you have created your webhook in Okta, your webhook should be status: ACTIVE, verification: VERIFIED - indicated by the response from the Okta API - then the webhook has been successfully configured between Okta and Azuqua.
    4. Trigger your webhook.

    Output Fields

    • Output
      • Date and Time (string): The date and time the webhook event was published.
      • Message (string): Message details about the event.
      • Admin: The Okta admin that provisioned the application membership.
        • ID (string): Admin user ID.
        • Alternate ID (string): Admin alternate ID (usually an email address).
        • Display Name (string): Admin display name.
      • Okta User: The Okta user that was added to the application.
        • ID (string): Okta user ID.
        • Alternate ID (string): Okta user alternate ID (usually an email address).
        • Display Name (string): Okta user display name.
      • Application User: The target application’s user details.
        • ID (string): Application user ID.
        • Alternate ID (string): Application user alternate ID (usually an email address).
        • Display Name (string): Application user display name.
      • Application: The target application for which a user is becoming a member of.
        • ID (string): Application ID.
        • Alternate ID (string): Application alternate ID.
        • Display Name (string): Application display name.
      • UUID: (string): Webhook event universally unique identifier (uuid).
      • Full Details (object): The entire payload returned from the Okta API for this webhook event. This is the raw JSON.
  • User Reported Suspicious Activity - Beta

    Okta - User Reported Suspicious Activity webhook event. Listen for the event triggered in Okta, that will trigger the FLO in real time.

    Note - The Okta webhooks are currently in beta.

    Important: Okta webhooks will only trigger one registered endpoint for any given event type, meaning if you have multiple FLOs and/or other event hook endpoints configured for one specific event type, Okta will only send a request to one of those endpoints. It is recommended that you only activate one endpoint per event type, otherwise all endpoints will not receive event notifications.

    Instructions

    1. In order to create an Okta Webhook, you will first need an accessible URL endpoint before configuring the Webhook in Okta. This can be done by creating a FLO using this webhook event, and then saving the FLO. Turn on the FLO (important). Click the ‘Webhook settings’ button at the bottom right of this card. This will present you with the Webhook URL. Copy the URL. Webhook Settings
    2. Provide the URL when configuring your Okta Webhook. Additionally, you must provide the event type: user.account.report_suspicious_activity_by_enduser.
    3. Once you have created your webhook in Okta, your webhook should be status: ACTIVE, verification: VERIFIED - indicated by the response from the Okta API - then the webhook has been successfully configured between Okta and Azuqua.
    4. Trigger your webhook.

    Output Fields

    • Output
      • Date and Time (string): The date and time the webhook event was published.
      • Name (string): The name of the user that reported the suspicious activity.
      • Email (string): The email of the user that reported the suspicious activity.
      • User ID (string): The ID of the user that reported the suspicious activity.
      • Suspicious Activity Details (string): Suspicious activity message details.
      • Full Details (object): The entire payload returned from the Okta API for this webhook event. This is the raw JSON.

Actions

  • Create User

    Creates a new user within Okta.

    Options

    • Option (dropdown list): Different ways to create a user including:
      • without Credentials
      • with Recovery Question
      • with Password
      • with Password & Recovery Question
      • with Authentication Provider
      • in Group

    For more detail on these options, or additional info regarding creating users in Okta, reference this documentation.

    Input Fields

    The input fields are dependent on the “Option” dropdown list selection, but will always include: First Name, Last Name, Email, Login. Required fields are shown with a red asterisk.

    • Profile
      • First Name (text): First name of the Okta user
      • Last Name (text): Last name of the Okta user
      • Email (text): Email address of the Okta user
      • Login (text): Login of the Okta user, must always be an email address format
      • Mobile Phone (text): Mobile phone of the Okta user, optional
    • Credentials
      • Question (text): Recovery question (must be specified if Answer is specified)
      • Answer (text): Recovery answer (must be specified if Question is specified)
      • Password (text): Password, must meet minimum criteria (see documentation referenced above)
      • Provider Name (text): Name of the identity provider,  ACTIVE_DIRECTORY or LDAP providers should specify the directory instance name
      • Provider Type (dropdown list): Identity provider type (choose from list)
    • Activate
      • Activate (boolean): Indicates whether the user should be treated as ‘activated’ upon creation, reference documentation above for more info on this

    Output Fields

    • Results
      • Raw Body (object): Raw payload returned from the Okta API
      • ID (text): ID of the user created in Okta
      • Status (text): Raw payload returned from the Okta API
      • Created (date): Raw payload returned from the Okta API
      • Activated (boolean): Raw payload returned from the Okta API
      • Status Changed (date): Date of the last time the user’s status changed
      • Last Login (date):Timestamp of the last login date of the user
      • Last Updated (date): Timestamp of the last updated date of the user
      • Password Changed (boolean): T/F designating if the user’s password is changed
  • HTTP Request

    Make an authenticated request to the Okta API.

    Options:

    • Request Type (dropdown): use the appropriate request type depending on the endpoint/method you are interacting with (reference Okta API for more details).
      • GET
      • POST
      • PUT
      • PATCH
      • DELETE

    Inputs:

    • Relative URL (text):The relative URL should be specified as “/api/v2/{insert remaining URL}”. You can specify query parameters in the relative URL using “?”, OR specify the query parameters as an object key pair in the Query input.
    • Headers (object): Specify any headers required in addition to authorization or content-type (these are already handled by this connector)
    • Query (object): Specify any additional query parameters that should be included in object format (key value pairs)

    Outputs:

    • Response
      • Status Code (number): Number code associated with state
      • Headers (object): Title/header for HTTP
      • Body (object): Raw output returned from Okta API
  • Search Users

    Searches for user(s) within Okta using query provided. The query performs a starts with match for any of the following: First Name, Last Name, or Email. The limit of records returned is 200. For more information review the Okta documentation here.

    Options

    • Option (dropdown list):
      • First Matching Record: returns a single record
      • All Matching Records: returns all matching records, in list format

    Input Fields

    • Inputs
      • Query (text): Query string used to find records, can be: first name, last name, or email address

    Output Fields

    • Result 
      • First Matching Record:
        • Raw Body (object): Raw payload returned from the Okta API
        • ID (text): ID of the user created in Okta
        • Status (text): Raw payload returned from the Okta API
        • Created (date): Raw payload returned from the Okta API
        • Activated (boolean): Raw payload returned from the Okta API
        • Status Changed (date): Date of the last time the user’s status changed
        • Last Login (date):Timestamp of the last login date of the user
        • Last Updated (date): Timestamp of the last updated date of the user
        • Password Changed (boolean): T/F designating if the user’s password is changed
      • All Matching Records:
        • Users (list of objects): All matching users with payload similar to above, in list format