Skip to content
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

Open
jorgesumle opened this issue Jan 21, 2018 · 7 comments
Open

Add Gitea as an elsewhere platform #943

jorgesumle opened this issue Jan 21, 2018 · 7 comments
Labels
linked accounts integration with other platforms

Comments

@jorgesumle
Copy link
Contributor

Gitea is free software like GitLab, so maybe we can use the same approach for issue #661

@6543
Copy link

6543 commented Jan 8, 2020

  • gitea.com
  • Codeberg.org
    ...

@Changaco Changaco added the linked accounts integration with other platforms label Feb 17, 2020
@Changaco
Copy link
Member

From https://docs.gitea.io/en-us/oauth2-provider/:

To use the Authorization Code Grant as a third party application it is required to register a new application via the “Settings” (/user/settings/applications) section of the settings.

Currently Gitea does not support scopes (see #4300) and all third party applications will be granted access to all resources of the user and his/her organizations.

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.

@6543
Copy link

6543 commented Feb 18, 2020

@Changaco

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

@revi
Copy link
Member

revi commented Feb 19, 2020

Currently Gitea does not support scopes (see #4300) and all third party applications will be granted access to all resources of the user and his/her organizations.

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.

@ncorder
Copy link

ncorder commented Nov 4, 2021

From https://docs.gitea.io/en-us/oauth2-provider/:

To use the Authorization Code Grant as a third party application it is required to register a new application via the “Settings” (/user/settings/applications) section of the settings.
Currently Gitea does not support scopes (see #4300) and all third party applications will be granted access to all resources of the user and his/her organizations.

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.

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.

@Akselmo
Copy link

Akselmo commented Jan 23, 2023

Any possibility to have pulling repositories from any gitea instance?

@jolheiser
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
linked accounts integration with other platforms
Development

No branches or pull requests

7 participants