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
When creating a SPA, the auth0_client_credentials resource gets created with authentication_method = "client_secret_post" by default. This issue suggests it should be created with "none", as appropriate for SPA.
Expectation
The authentication_method should be set to "none" for a SPA.
Reproduction
Given a resource defined like so:
resource"auth0_client""frontend_client" {
name="name"description="description"client_metadata={} # some real values hereapp_type="spa"# filled with real valuesinitiate_login_uri=""callbacks=[]
allowed_origins=""allowed_logout_urls=""web_origins=[]
oidc_conformant=truelogo_uri="logo_uri"grant_types=[
"refresh_token",
"authorization_code",
"http://auth0.com/oauth/grant-type/mfa-otp"
]
is_first_party=truejwt_configuration {
alg="RS256"
}
refresh_token {
rotation_type="rotating"expiration_type="expiring"token_lifetime=43200# 12 hoursidle_token_lifetime=28800# 8 hoursinfinite_idle_token_lifetime=false
}
}
When the resource is created, the token endpoint authentication method is set to client_secret_post instead of none.
This can be consistently reproduced.
Auth0 Terraform Provider version
1.0.0
Terraform version
1.5.6
The text was updated successfully, but these errors were encountered:
Checklist
Description
When creating a SPA, the
auth0_client_credentials
resource gets created withauthentication_method = "client_secret_post"
by default. This issue suggests it should be created with "none", as appropriate for SPA.Expectation
The
authentication_method
should be set to "none" for a SPA.Reproduction
Given a resource defined like so:
When the resource is created, the token endpoint authentication method is set to
client_secret_post
instead ofnone
.This can be consistently reproduced.
Auth0 Terraform Provider version
1.0.0
Terraform version
1.5.6
The text was updated successfully, but these errors were encountered: