-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuth2 Compliance Imporvements #4535
Comments
I would also be in favor of full OpenID Connect support. |
Any updates on this? |
It's posible to create workaround for OpenID in small steps. I'm operating with docker. So you should copy data/web/oauth/profile.php to data/web/oauth/profile-openid.php Than replace the scope for your needs, for example to You will get something like this:
Then you can use profile url like this https://example.com/oauth/profile-openid |
Summary
Here is a list of OAuth2 Compliance Improvements:
Motivation
This is needed for example by Apache 2 auth_auth_openidc and it would be achievable. It would render OAuth2 usable.
Additional context
{
"issuer": "https://mail.lesgrandsvoisins.com",
"authorization_endpoint": "https://mail.lesgrandsvoisins.com/oauth/authorize",
"token_endpoint": "https://mail.lesgrandsvoisins.com/oauth/token",
"userinfo_endpoint": "https://mail.lesgrandsvoisins.com/oauth/profile",
"revocation_endpoint": "",
"jwks_uri": "this is the kicker for me",
"response_types_supported": [
"code",
"token",
"id_token",
"code token",
"code id_token",
"token id_token",
"code token id_token",
"none"
],
"subject_types_supported": [
"public"
],
"id_token_signing_alg_values_supported": [
"RS256"
],
"scopes_supported": [
"profile"
],
"token_endpoint_auth_methods_supported": [
"client_secret_post",
"client_secret_basic"
],
"claims_supported": [
"aud",
"email",
"email_verified",
"exp",
"family_name",
"given_name",
"iat",
"iss",
"locale",
"name",
"picture",
"sub"
],
"code_challenge_methods_supported": [
"plain",
"S256"
],
"grant_types_supported": [
"authorization_code",
"refresh_token",
"urn:ietf:params:oauth:grant-type:device_code",
"urn:ietf:params:oauth:grant-type:jwt-bearer"
]
}
The text was updated successfully, but these errors were encountered: