<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
0D54z00007Fe5gkCABOkta Identity EngineWorkflowsAnswered2022-03-09T20:39:40.000Z2021-10-21T17:51:39.000Z2021-11-19T01:06:36.000Z
Save output for later use

I'm building a workflow to offboard users from our Adobe Org when they are deactivated in Okta. What I'm having issues with are saving the JWT token that needs to be refreshed every 24 hours, then using it for the rest of the api calls. I would like the JWT Token generation and exchange to stay separated from the parent flow of deactivated users.

 

Currently the Adobe Offboarding flow is a child flow of the Deactivated Users flow. Is there a way to save the output generated from a non-parent or non-child flow to be used in another flow? Kind of like a variable?


  • SathishK.23283 (Customer)

    Please store it in a table. Okta has tables next to the flow. It will be helpful. To be honest, 'Okta workflows are Super 🙂 and most powerful'

  • TimL.58332 (Workflows)

    As Sathish mentioned you can leverage a table. You can encrypt the token prior to storing. However, you will still need to leverage the "key/password" in plain text within the flow to encrypt/decrypt. One thing to keep in mind is Workflows access is limited to Super Administrators which does reduce exposure.

This question is closed.
Loading
Save output for later use