Hi Mads,

Can you try to follow the in-product documentation to get this setup? The link is below, but you can also find it during the Okta connection setup screen and by clicking the ? in the bottom left.

https://learn.workflows.okta.com/connector-reference/okta/#auth

Go to the section titled "Authorize an account from another Okta org". In the meantime, we'll try to see what's incorrect about the knowledge base article.

Arvil

Thanks Arvil,

I take that as it is supposed to work, and it is not working for us. Thanks for the link, I had that site opened, but had failed to find that part. Excellent instructions*. I reviewed and found no apparent wrongs on our end. I deleted the connector and the OAuth App on the target and did them over, following the guide. Alas, no dice, and I get an error message "Could not activate Flow" when I try to activate it. I'll take this to Okta Support to have them have a look. I'll keep you posted on the result.

*Some suggested corrections

This isn't correct (any longer)

It should say: Your OpenID Connect web app > General tab > Client Credentials

Thanks,

Mads

@q5nrb (q5nrb)​ 

Thanks for bringing this to our attention, the guide you followed was out of date and has been removed.

This is the guide for setting up Okta connections in Workflows: https://help.okta.com/en/prod/Content/Topics/Workflows/connector-reference/okta/overviews/authorization.htm.

Right, finally back from summer break, and Okta support had the solution ready waiting for me. It was insufficient Okta API Scope permissions. Both the okta.eventHooks.manage and okta.eventHooks.read needed to be granted. After re-authorization of the connector, the flow activates and works just fine.