-
-
Notifications
You must be signed in to change notification settings - Fork 219
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 Gitea as an elsewhere platform #943
Comments
|
From https://docs.gitea.io/en-us/oauth2-provider/:
So, we can't automatically create OAuth credentials for Liberapay, and users would have to agree to give Liberapay write access. In other words, Gitea doesn't provide what we need for a good integration. |
dont think so: only one user (best would be a admin of librepay) has to create an OAuth app in his user settings for the Oauth credentials and now every user can use this OAuth source |
We want to have minimum scope we can have (which is basically read only access to basic information), and since we are not going to write anything, we probably should not have write access - so nothing can be done with the credentials if some really bad things (tm) happens and our DB is compromised. |
I'm not certain if I have much to add to this conversation. But it is possible for Liberapay to ask users to remove the application OAuth keys after they have verified an account. Gitea and NotABug and many other platforms also utilize Libravatar and allow users to include domains and other information which might be able to be used to verify them. |
Any possibility to have pulling repositories from any gitea instance? |
Also stopping by to mention that we've merged go-gitea/gitea#20908 which allows for scoped tokens, which should address some of the other concerns here. |
Gitea is free software like GitLab, so maybe we can use the same approach for issue #661
The text was updated successfully, but these errors were encountered: