Okta Inline Hook Fails With "The endpoint did not respond in time" Error
Last Updated:
Overview
An Okta Inline Hook fails when the basic authentication header or secret token that Okta sends to the inline hook endpoint is invalid or expired. Resolve this issue by verifying and updating the authorization header or secret key in the Okta Admin Console. During execution, the hook process terminates, and the Okta System Log displays an error message in the Dashboard when configuring the inline hook request and preview responses.
The Dashboard displays the following error message when configuring the inline hook request and preview responses:
Hook "<hook-name>" execution failed. Remote server responded with client error, responseCode= 403 message=Forbidden
The System Log displays the following error message:
Inline Hook execution failed
FAILURE: Hook "<hook-name>" execution failed. The endpoint did not respond in time. Check endpoint performance.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- API Access Management
- Inline Token Hooks
Cause
This error could be happening because the basic authentication header or secret token that Okta sends to the inline hook endpoint is invalid or expired.
Solution
How is the endpoint did not respond in time error resolved?
Verify the authorization header or secret key configured in the Okta Admin Console to ensure the credentials match the endpoint expectations.
- Navigate to Workflow > Inline Hooks in the Okta Admin Console.
- Choose the affected hook.
- Verify the authorization header or secret key to ensure the credentials match the endpoint expectations.
