-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add support for Gitea OAuth #33
Comments
Just briefly glancing at the project structure, it seems like OAuth is provided by your external library, https://github.com/nektro/go.oauth2 There's nothing wrong with this, but the project doesn't seem to have support for configuring providers with a custom hostname, which means adding this kind of support isn't 100% drop in addable without a few structure changes. In other words, it might be involved. |
Since GitTea is a self-hosted service it cannot be added to nektro/go.oauth2 as a pre-loaded identity provider, but I also just created #34 which should solve this issue and support more self-hosted services in the future. |
A section will be needed to be added to |
Alright, so long as there's a solution. |
As long as this is a project for self-hosted open directories, we might as well add support for self-hosted github-like services like Gitea: https://docs.gitea.io/en-us/oauth2-provider/
Shouldn't require anything complex on top of what the Github OAuth already does other than the ability to configure the Gitea instance hostname in
config.json
, which is arguably what the Github configuration should already have since self-hosted Github Enterprise is a thing.The text was updated successfully, but these errors were encountered: