Okta Custom HTTP OAuth Connector Fails Authentication after Attempting to Refresh the Token
Mar 12, 2026
Workflows
Okta Classic Engine
Okta Identity Engine
Overview
This article explains why a custom HTTP OAuth connector is unable to refresh the token and fails authentication after the initial token expires.
Applies To
- Okta Workflows
- HTTP OAuth connector
Cause
The scopes defined for the custom HTTP OAuth connector do not allow token refresh.
Solution
- Click re-authorize HTTP connector from Workflows > Settings screen.
-
Add
offline_access(or whatever the vendor has provided that allows for token refresh) as part of the scopes defined for the HTTP OAUTH connector. Scopes are generally added as a space or comma-delimited set of scopes. -
Add the rest of the URL/credentials information.
-
Click save (if the service provider supports the
offline_accessscope, the authorization screen will appear; if not, an error will show. If so, contact the vendor to determine their scope for this access).
