Decouple the username hash from the login given
Hi all,
Is there a way to do the hash on the director without setting the user (or destuser) for the Dovecot backend authentication?
The scenario is:
Our accounts have multiple aliases where each alias can have a different password (long story):
Alias1 accountX password1 Alias2 accountX password2 Alias3 accountX password3 accountX accountX passwordX
Our goal is to map the same account, regardless of the alias used to authenticate, to the same backend server.
We use checkpassword for userdb on the director, and when we set either the user or username to the main account id (accountX on the example) it sends the authentication as accountX, passwordN, and fails.
Is there a var that can be set and used for hashing, leaving the authentication untouched?
Our installed version is 2.3.21.
Thank you.
Best regards, José Celestino
Just to add some info, I tried:
setting director_username_hash=accountX on the checkpasswd env + extra, but the director just uses the conf version (seemed like a decent solution though)
setting username on checkpasswd env + extra and destuser=%{original_user} on the passdb { override_fields } but then it just uses the destuser (which is the given user login, not necessarily accountX) both for the hash and the backend login
On 8 Apr 2025, at 18:51, José Celestino via dovecot <dovecot@dovecot.org> wrote:
Atenção: Este email foi originado fora da MEO SGPS, S.A. Por favor, não clique em links nem abra anexos, a não ser que conheça o remetente e saiba que o seu conteúdo é seguro.
Hi all,
Is there a way to do the hash on the director without setting the user (or destuser) for the Dovecot backend authentication?
The scenario is:
Our accounts have multiple aliases where each alias can have a different password (long story):
Alias1 accountX password1 Alias2 accountX password2 Alias3 accountX password3 accountX accountX passwordX
Our goal is to map the same account, regardless of the alias used to authenticate, to the same backend server.
We use checkpassword for userdb on the director, and when we set either the user or username to the main account id (accountX on the example) it sends the authentication as accountX, passwordN, and fails.
Is there a var that can be set and used for hashing, leaving the authentication untouched?
Our installed version is 2.3.21.
Thank you.
Best regards, José Celestino
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
AVISO DE CONFIDENCIALIDADE Esta mensagem e quaisquer ficheiros anexos a ela contêm informação confidencial, propriedade do grupo MEO e/ou das demais sociedades que com ela se encontrem em relação de domínio, Fundação MEO e MEO ACS, destinando-se ao uso exclusivo do destinatário. Se não for o destinatário pretendido, não deve usar, distribuir, imprimir ou copiar este e-mail. Se recebeu esta mensagem por engano, por favor informe o emissor e elimine-a imediatamente. Obrigado
participants (1)
-
José Celestino