[Akkoma] - Can not log in with email #403

Open
opened 2022-12-29 18:19:11 +01:00 by meaz · 10 comments
Owner

On https://fe.disroot.org, it is mentionned that you can log in with username or email, but email doesn't work.

On https://fe.disroot.org, it is mentionned that you can log in with username or email, but email doesn't work.
meaz added the
Akkoma
label 2022-12-29 18:19:11 +01:00
muppeth was assigned by meaz 2022-12-29 18:19:23 +01:00
Owner

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.

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.
Author
Owner

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)

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)
meaz added this to the 23.02 - February milestone 2023-01-29 10:06:42 +01:00
muppeth added this to the 23.02 - February project 2023-02-15 22:49:05 +01:00
muppeth modified the milestone from 23.02 - February to 23.03 - March 2023-03-01 21:01:12 +01:00
muppeth removed this from the 23.02 - February project 2023-03-01 21:01:16 +01:00
Author
Owner

@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?

@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?
Owner

We could just do the frontend fix. At least temporarily till it can be definitely solved on LDAP.

We could just do the frontend fix. At least temporarily till it can be definitely solved on LDAP.
Author
Owner

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 to username only), and would be overwritten when we update the software. Unless @muppeth has a better solution.

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 to `username` only), and would be overwritten when we update the software. Unless @muppeth has a better solution.
Author
Owner

@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.

@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.
muppeth added this to the 23.03 - March project 2023-03-08 12:13:11 +01:00
muppeth removed this from the 23.03 - March milestone 2023-04-05 19:51:00 +02:00
muppeth removed this from the 23.03 - March project 2023-04-10 12:21:26 +02:00
Author
Owner

in the meantime I created an issue on https://akkoma.dev/AkkomaGang/akkoma/issues/667

in the meantime I created an issue on https://akkoma.dev/AkkomaGang/akkoma/issues/667
Owner

Do we still keep it open or close it since there was no reply on feature request so far?

Do we still keep it open or close it since there was no reply on feature request so far?
Author
Owner

I would keep it as a placeholder.

I would keep it as a placeholder.

@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.

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.

> @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. 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.
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#403
No description provided.