client secret

• Test OIDC client connection:

curl -s -X POST https://<OKTA_DOMAIN>/oauth2/v1/token \
       -d "grant_type=authorization_code" \
       -d "code=invalid-test" \
       -d "client_id=<CLIENT_ID>" \
       -d "client_secret=<CLIENT_SECRET>" \
       -d "redirect_uri=https://placeholder/callback" | jq

invalid_grant is a valid response

If you have not assigned client_id or client_secret, A SystemAssigned identity will be created.

• https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-client-creds-grant-flow

The client secret that you generated for your app in the app registration portal. The client secret must be URL-encoded before being sent. The Basic auth pattern of instead providing credentials in the Authorization header, per RFC 6749 is also supported.

Related

• The Client ID and Secret
• az aks
• grafana_sso_settings
• Configure Generic OAuth authentication in Grafana
• var.client_id
• Issuer URL

See also

• IdP <-> RP, client_id, client_secret, Issuer URL, QUARKUS_OIDC_CLIENT_ID, .well-known/openid-configuration, grant_type
• OpenID Connect (OIDC), kubectl oidc-login, AWS IAM OIDC, EKS OIDC, EKS module, aws iam list-open-id-connect-providers | aws iam create-open-id-connect-provider | aws iam get-open-id-connect-provider, OIDC tokens, aws_lb_listener_rule, Google Cloud Identity, Claims, keycloak_oidc_identity_provider, settings, OIDC client, client_id, client_secret, Authorization Code Flow, OIDC Web App, Back-Channel