You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2022. It is now read-only.
The Oauth2 provider is not supported. When it is used it throws the following error Error: 400 Bad Request: Payload validation error: 'Missing required property: options'.
New or Affected Resource(s)
auth0_connection
Potential Terraform Configuration
basically just taking the OIDC configuration and just use the fields needed by the generic oauth2 connection
# Copy-paste your Terraform configurations here - for large Terraform configs,# please use a service like Dropbox and share a link to the ZIP file. For# security, you can also encrypt the files using our GPG public key.resource"auth0_connection""my_con" {
name="my_con"strategy="oauth2"realms=["my_con"]
is_domain_connection=falseenabled_clients=["xxx"]
options {
client_id="xxx"client_secret="xxx"scopes=["openid", "profile", "email"]
token_endpoint="https://xxx.com/oauth2/token",
authorization_endpoint="https://xxx.com/oauth2/authorize"custom_scripts={
fetchUserProfile ="..."
}
custom_headers={
"x-header"="xxx"
}
}
}
References
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Description
The Oauth2 provider is not supported. When it is used it throws the following error
Error: 400 Bad Request: Payload validation error: 'Missing required property: options'.
New or Affected Resource(s)
Potential Terraform Configuration
basically just taking the OIDC configuration and just use the fields needed by the generic oauth2 connection
References
Community Note
The text was updated successfully, but these errors were encountered: