Repository navigation
[FEATURE] support Yandex OAuth provider #1043
Description
Activity
Hello @Lex-2008,
Tinyauth does not support OIDC providers that don't follow the OIDC specification. The only exceptions that have been made are for Google and GitHub which are what everybody uses pretty much. For now, maintaining a fork is the solution but we could eventually support claim mapping for such providers.
Reacted by Aleksei ShpakovskiiUpdate, with good news. Decided adding custom claims was not that hard...so I did #1087. With the next version of Tinyauth you should be able to do:
TINYAUTH_OAUTH_PROVIDERS_name_CLAIMS_USERNAME=default_email TINYAUTH_OAUTH_PROVIDERS_name_CLAIMS_EMAIL=default_email TINYAUTH_OAUTH_PROVIDERS_name_CLAIMS_NAME=default_email
However, I am not sure if I should also add the
subclaim because then we are kind of shifting completely from the OIDC specification.
Is your feature request related to a problem? Please describe.
First, thank you for this wonderful little project! (pun intended)
Describe the solution you'd like.
In my fork, I've added support for Yandex OIDC provider, commit. They have a non-standard oidc implementation: you have to request
login:emailas scope, and they provide it indefault_emailclaim.I wonder if you'll like a PR with a change like this, or would you prefer to keep the list of "special case" oidc providers to minimum.
Describe alternatives you've considered.
Now that i looked at it deeper, I think this could also be fixed by #1025
Additional context
No response
Human Written Confirmation