Okta 403 Error Occurs When Creating Event Hooks With Custom Roles
Last Updated:
Overview
An API application that uses a custom role to manage event hooks generates a 403 error when attempting to create an event hook. This occurs because the custom role lacks the necessary inline hook management permissions. Resolve this issue by assigning the Manage inline hooks permission to the custom role. Specifically, an API application (machine-to-machine) with public key authentication contains scopes such as okta.eventHooks.manage and uses a custom role with the Manage EventHooks permission. When the service requests an access token and attempts to create an event hook, Okta generates a 403 error.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Custom Admin Roles
- Event Hooks
- API Applications
Cause
The custom role used by the API application contains only the Manage EventHooks permission. Creating event hooks also requires the Manage inline hooks permission.
Solution
What steps resolve the 403 error when creating event hooks?
Resolve the 403 error by navigating to the custom role settings in the Admin Console and adding the inline hooks management permission.
- Open the Admin Console.
- Go to Security, and then select Administrators.
- Select the Roles tab.
- Choose the custom role that the API application uses.
- Edit the role to include the Manage inline hooks permission.
- Save the changes.
