Open richard-collette-precisely opened 3 weeks ago
This example of an OAuth inline hook seems to be completely inaccurate because it does not include clientId, clientSecret, etc.
It appears as there are no OAUTH tests
I think that before update the documentation the OAUTH2 configuration need to be implemented in the provider. Actually, there are no capability to define secret information with the oAuth2 type.
OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-826990
Community Note
Description
The inline hook resource has two properties, auth and channel, that are of type map and therefore do not provide strict typing or documentation of the properties to be used when configuring:
Further hindering the ability to determine proper configuration, is the fact that the structure of the underlying API that is used:https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createInlineHook
does not match the structure used for the inline hook resource definition.
New or Affected Resource(s)
Non-working Terraform Configuration
The following configuration generated from Terraform CDK
results in the following http request, which is missing channel.config values for many of the OAuth related properties such as clientId, clientSecret, etc.