[Akkoma] - Can not log in with email #403
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#403
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On https://fe.disroot.org, it is mentionned that you can log in with username or email, but email doesn't work.
That will be interesting to solve. We could solve it in two ways:
In frontend which could be done and I am capable to do it right (upstream it and add to options etc). Or tweak LDAP authenticator to allow mail attribute lookup.
Although frontend solution seems easier to fix from my standpoint. LDAP solution is I think proper way to do about it. I will rather look into that and perhaps be able to add/fix other things to allow aliases for example.
I'd go for the LDAP solution too, especially as lot of people messed up between email ond username (like on user.disroot.org, they always enter username@disroot.org instead of username)
@muppeth I'm re-reading your answer: when you write about
tweak LDAP authenticator to allow mail attribute lookup
you mean on our ldap or on akkoma LDAP plugin?We could just do the frontend fix. At least temporarily till it can be definitely solved on LDAP.
I've checked for a temporary fix but it requires changing
header.login.username.placeholder
on all languages files, which isn't the best solution (we just change the displaying test tousername
only), and would be overwritten when we update the software. Unless @muppeth has a better solution.@muppeth could this issue be related to the one we also have with nextcloud: there also, we can not log in with email, it has to be username, whereas it is said that we can log in with both.
in the meantime I created an issue on https://akkoma.dev/AkkomaGang/akkoma/issues/667
Do we still keep it open or close it since there was no reply on feature request so far?
I would keep it as a placeholder.
Sorry to be a little off-topic, but is the Nextcloud log in issue (using the email address) tracked in another issue? If so, I couldn't find it.
I am asking because I wanted to report if few times (I find it quite annoying) and accidentally find this reference here.