Workflow API Connector back into Okta 403 Forbidden

Questions API
1

The standard workflow card for updating an account won’t do what I need. An API will do what I need. Therefore I created a workflow API Connector. When I try to GET a user account, I get 403 Forbidden. I am using same URL and Headers that I use with Postman.
What do you think is happening?
How can permissions be missing?

{
“retry_count”: 0,
“flo”: “httpfunctions:1.0.13:get”,
“method”: “_uDslKobqBp”,
“execution”: “0a66eb7b-3ebf-4709-83b2-aafb884d92c5”,
“module”: “http.call”,
“kind”: “HTTP Request Error”,
“statusCode”: 403,
“headers”: {
“content-type”: “application/json”,
“public-key-pins-report-only”: "pin-
…
},
“body”: {
“errorCode”: “E0000005”,
“errorSummary”: “Invalid session”,
“errorLink”: “E0000005”,
“errorId”: “oaerk4MCZf0SZaZW1HXC6N-2g”,
“errorCauses”:
},
“message”: “403 Forbidden”,
“description”: “HTTP Request Error”,
“steps”: 32,
“source”: {
“flo”: “httpfunctions:1.0.13:get”,
“method”: “_uDslKobqBp”,
“execution”: “0a66eb7b-3ebf-4709-83b2-aafb884d92c5”,
“module”: “http.call”
}
}

2

Hello Scott!

It looks like maybe the authentication itself on your connector is having difficulty. Do you have the redirect_uri added into any app you might be using to authenticate? What happens if you set up the authentication again?

It may be easier to use the Okta Connector: Okta connector | Okta - you should be able to choose “Custom API Call” here and customize the API call how you need.

1 Like
3

I opened a Case and discovered that only needed to set the API Connector to use Auth Type = None . I think I was previously using Basic.

4

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.