Clarification
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2024 02:19 AM
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
Lookup user id held in system property
Call action “Is User Account Locked” (input user id from previous step)
If the step returns “invalid token”
Generate URL
Record ID: Current flow engine context ID
Table Name: sys_flow_context
Display: Flow Context Error Record
create and Incident record assigned to the ServiceNow team
Caller: ServiceNow Automation
Channel: Event
Assigned Group: ServiceNOW
Category: Failure
Configuration Item: ServiceNow (Business Service Class)
Short Description: Okta Integration failed with Invalid Token
Description: The Okta Integration Keep-alive flow has failed due to Invalid Token
Urgency: 2
Impact: 3
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#”