Invalid credentials error when signing in to non-LDAP accounts

[Graycot]

Problem: After registering a non-YunoHost/LDAP Akkoma account, signing in throws a "Invalid Credentials" error.

Solution: Go to the Admin FE > Settings > Authentication > LDAP > Toggle off "Enabled".

Note: Signing in with the original LDAP connected admin account is not affected by disabling LDAP, and works as normal.

[bugsysop]

Workerd for me with Pleroma, but not with Akkoma.

Worked like a charm on a new install of Akkoma.
On the old one I possibly messed up the config playing with to many options.

[lapineige]

Do you use a password with special characters @Graycot ?

[Graycot]

Do you use a password with special characters @Graycot ?

No, I did not.

[lapineige]

So if I understand correctly :

• you create a first user that is from LDAP (how ? I didn't know that was working).
• login works
• then you create another account
• and then it fails ?

Which version are you using ?

#12 fixed a syntax error in LDAP config, maybe that changed something ?

[tio-trom]

Same here with the latest 3.7.1~ynh1 version. My config looks like this:

config :pleroma, Pleroma.Web.Auth.Authenticator, Pleroma.Web.Auth.LDAPAuthenticator
config :pleroma, :ldap,
  enabled: true,
  host: "localhost",
  port: 389,
  ssl: false,
  # sslopts: [],
  tls: false,
  # tlsopts: [],
  base: "ou=users,dc=yunohost,dc=org",
  uid:  "uid"

If I try to set enabled: false it still does not work. Is there a way to entirely remove LDAP from Akkoma?

Edit: I am stupid. I should have read the docs and the main comment here. Works now. Sorry.

[lapineige]

What was the issue ?

[tio-trom]

What was the issue ?

For me trying to login with non LDAP users. Would not work. Disabling LDAP entirely fixes the issue.

[Graycot]

What was the issue ?

For me trying to login with non LDAP users. Would not work. Disabling LDAP entirely fixes the issue.

This is the issue and solution I experienced.

[lapineige]

I hope recent config change would fix it… if anyone can try a fresh install of #28… or check their /etc/akkoma/config.exs file and see if this part it's the same as in https://github.com/YunoHost-Apps/akkoma_ynh/blob/2023.04/conf/ldap.exs

[lapineige]

Thanks for sharing the workaround, because I suddenly encountered this issue recently… it was quick and easy to identify and fix it thanks to you.

I wonder if we should disable LDAP by default until we integrate it properly 🤔

[lapineige]

As a side note, I had to dump instance config from database, change the values, then migrate config file to db again, as I would have lost my settings (done from the admin UI) it if I migrated the config file first.
Here are the commands (adapt them according to our Readme) : https://docs-develop.pleroma.social/backend/administration/CLI_tasks/config/