<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009pS6YpCAKOkta Identity EngineIdentity GovernanceAnswered2024-04-16T19:30:20.000Z2023-11-09T18:20:55.000Z2023-11-09T22:49:05.000Z

MaeP.56501 (Customer) asked a question.

Creating Pre-Expiration Notification for OIG Requests Using Okta Workflows

One major gap we're seeing within the OIG platform is the lack of a notification at a set point before application or group access is removed at the end of a set timer. We'd like to create a workflow that scrapes open requests for user/application/expiration date and sends them a slack message to the user a week before the expiration with the details.

 

Has anyone created something like this already or have feedback on what this could look like?


  • TimL.58332 (Workflows)

    If I were solving for this use case I would go about this differently. I would create a total of 3 flows & one table.

     

    Table - Shared between the 2 (top level) flows. Create columns to hold pertinent information for sending out your notification.

     

    Flow #1 - Delegated flow. Input is "email" (possibly other inputs just depends what you need to pass in from OIG). This flow would be used to populate the Table with the relevant information.

     

    Flow #2 (Parent) - This would run on a schedule. It would "Search" the table column that contains the "Date" when they will be actioned against by OIG. It would then (for each) the results to the helper.

     

    Flow #3 (Helper) - This flow would process each found result from Flow2 (parent) including sending out the email and removing the row from the table.

    Expand Post
This question is closed.
Loading
Creating Pre-Expiration Notification for OIG Requests Using Okta Workflows