When --oidc-type=embedded, the --oidc-issuer-url must end with /oidc for OIDC discovery to work correctly. Currently, there's no validation, leading to confusing errors like the one shared below.
{
"success": false,
"error": "oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html; charset=utf-8\": invalid character '<' looking for beginning of value"
}
The current embedded OIDC provider hardcodes all OIDC endpoints with the /oidc path prefix, if not present in the issuer-url, it causes OIDC discovery to fail.
When
--oidc-type=embedded, the--oidc-issuer-urlmust end with/oidcfor OIDC discovery to work correctly. Currently, there's no validation, leading to confusing errors like the one shared below.The current embedded OIDC provider hardcodes all OIDC endpoints with the
/oidcpath prefix, if not present in the issuer-url, it causes OIDC discovery to fail.