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

Mastodon OAuth implementation has no handling for the email field. #483

Open
chizutan5 opened this issue Nov 23, 2022 · 0 comments
Open

Comments

@chizutan5
Copy link

According to my code reading skills, the mastodon oauth implementation on Goth has no handing for the email field, this creates what I believe is a bug on Gitea where you cannot create a gitea account with a mastodon oauth session because it will ask for the email, however you can link a mastodon authententication session to an existing gitea account which already will have an email attached.
I have documented this issue at go-gitea/gitea#21710

Pleroma (or akkoma/newroma/rebased) instances and possibly mastodon too (I am not able to test), which are otherwise compatible with mastodon auth clients, will not provide an email to the client and as such cause this problem.
We should take the user's fediverse userid (user@instance.tld) and apply this to the email field, in the same way as pronouns.page handles its own custom mastodon login, or optionally allow the user to enter their own email address in.

I would offer to pull request but I don't know the first thing about go, I was only barely able to get a custom php implementation with mediawiki working with much outside help.

chizutan5 added a commit to chizutan5/goth that referenced this issue Dec 21, 2022
chizutan5 added a commit to chizutan5/goth that referenced this issue Dec 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant