Clarification

shaik17
Tera Contributor

Hi guys can any one explain this requirement,

The Okta API will lock out the token if it is not utilized for 30 days. We want a schedule flow created that will run a basic Okta function. Create a system property that will hold the test ID we will use for the action

sys_properties entry

  • Name: eplus_okta_test_user_id

  • Description: User ID used in the Okta API Heartbeat Test flow to verify the Okta Token is valid

  • value: TestUser@example.com

 

Flow scheduled to run every 25 days

  • Name : Okta API Heartbeat Test

  • Run AS: System Administrator

  1. Lookup user id held in system property

  2. Call action “Is User Account Locked” (input user id from previous step)

  3. If the step returns “invalid token”

    1. Generate URL

      1. Record ID: Current flow engine context ID

      2. Table Name: sys_flow_context

      3. Display: Flow Context Error Record

    2. create and Incident record assigned to the ServiceNow team

      1. Caller: ServiceNow Automation

      2. Channel: Event

      3. Assigned Group: ServiceNOW

      4. Category: Failure

      5. Configuration Item: ServiceNow (Business Service Class)

      6. Short Description: Okta Integration failed with Invalid Token

      7. Description: The Okta Integration Keep-alive flow has failed due to Invalid Token

      8. Urgency: 2

      9. Impact: 3

      10. Work Notes: “Review the Context Error Record and take appropriate action. The Token is most likely locked on the Okta Side.
        #'Code' output from the generate URL step noted above#”

0 REPLIES 0