<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
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z00007x8UQ3CAMOkta Identity EngineWorkflowsAnswered2026-06-03T22:16:02.000Z2022-08-22T13:32:41.000Z2026-06-03T22:16:02.000Z

MärtenH.64512 (Customer) asked a question.

August 22, 2022 at 1:32 PM
Okta Workflows oauth issues

Hi,

 

I'm having issues with setting up an API connector to connect Okta workflows to Sailpoint's IdentityNow. IDN supports multiple oath methods and seemingly it should fit with what Workflows supports as well.

 

After setting up the api token in IDN, with the redirect URI specified here: https://help.okta.com/wf/en-us/Content/Topics/Workflows/function-reference/HTTP/http_authorization.htm and filling in the oauth info, I'm been unable to process any further. If I click on "Create" , it opens a separate window that authenticates to IDN and then redirects to Workflows where I get a 404 not found response.

This is the address: https://transferwise.workflows.oktapreview.com/app/oauth/httpfunctions/[object%20Object]?scope=sp%3Ascopes%3Aall%20sp%3Ascopes%3Adefault&response_type=code&state=dHJhbnNmZXJ3aXNlLndvcmtmbG93cy5va3RhcHJldmlldy5jb206NDQzfDk5ZjZhZDA4LWQ0MTgtNDMyYS1hZGMxLWExNjljZDljMzBkMg%3D%3D&redirect_uri=https%3A%2F%2Foauth.workflows.oktapreview.com%2Foauth%2Fhttpfunctions%2Fcb&client_id=%5Bobject%20Object%5D where I end up.

 

I can't really tell what's going wrong since I don't have much visibility into what Workflows is attempting to do.

 

Any idea what I might be doing wrong?

  • 5 answers
  • 1.05K views

  • TimL.58332 (Workflows)

    Take a look at the following article:

    https://support.okta.com/help/s/article/How-to-Authenticate-with-HTTP-Cards-Okta-Workflows?language=en_US

     

    Also note. Workflows only supports Authorization Code Flow. If it is another grant type you would need to leverage "no auth" and have to build out the entire logic.

     

    Additionally, your mention of "Token" makes me think you are not trying to implement Oauth. A link to their auth documentation would be quite helpful.

    Expand Post

  • M√§rtenH.64512 (Customer)

    I eventually managed to get an "invalid scopes" error (only visible in the url) by hitting the Create button a multitude of times. Replaced scopes with sp:scopes:all and now I simply get a "Failed to create a connection" after the pop-up window disappears.

  • TimL.58332 (Workflows)

    So the key point in the linked article is the following. Those should be used as-is for the redirect URI (Depending on prod/preview org).

     

    Redirect URIs to connect to Okta Workflows Preview and Prod respectively: https://oauth.workflows.oktapreview.com/oauth/httpfunctions/cb and https://oauth.workflows.okta.com/oauth/httpfunctions/cb.

     

    The rest of the information should be derived from the vendor. For example the following link shows you where to get your authorize / token endpoints.

     

    https://developer.sailpoint.com/docs/authentication.html

     

    All that is left at that point is the client id/secret & scopes.

     

    Based on this:

    • sp:scopes:default
    •  - default scope
    • sp:scopes:all
    •  - access to all scopes

     

     

    Looks like "all" is the scope I would see if I could get working.

     

    Expand Post
    Selected as Best

  • M√§rtenH.64512 (Customer)

    I set up another API client with the same settings as the previous one, same redirect URI and all - except I _only_ included AUTHORIZATION_CODE grant_type, previously I had included them all when testing.

     

    Not sure if that's what was going wrong last time but now it works.

     

    Thanks for the help and thinking along

    Expand Post
This question is closed.
Loading
Okta Workflows oauth issues