Re: CYRADM: badlogin: OTP [SASL(-13): user not found: no OTP secret indatabase] BUT sasldblistuser2 proves passwd is set

Ken Murchison schrieb:
> Dennis Leist wrote:
>
> > Dear all,
> >
> > Please help in this issue:
> >
> > Trying set up mailboxes via cyradm
> >
> > # cyradm --user cyrus localhost
>
>
> Try:
>
> # cyradm --user cyrus --auth login localhost
This leads to:

IMAP Password:
              Login failed: generic failure at 
/usr/lib/perl/5.6.1/Cyrus/IMAP/Admin.pm line 114
cyradm: cannot authenticate to server with login as cyrus

> > always ends in
> >
> > # cyradm: cannot authenticate to server with  as cyrus
> >
> > I get  /v/l/imapd.conf:
> >
> > Jan 30 12:14:00 helium imapd[17700]: accepted connection
> > Jan 30 12:14:01 helium imapd[17700]: badlogin: localhost[127.0.0.1] OTP
> > [SASL(-13): user not found: no OTP secret in database]
> >
> > But sasldblistuser2 shows:
> >
> > #> sasldblistusers2
> > cyrus@helium: userPassword
> > cyrus@helium: cmusaslsecretOTP
>
>
> Did you specifically tell saslpasswd2 to use ony 'helium' as the realm,
I added cyrus with:
#> saslpasswd2 -c cyrus

and
#> saslpasswd2 -u helium.epag.net -c cyrus.

Another account with FQDN:

#> saslpasswd2 -c -u helium.epag.net cyrus

didn't help.
> or is the hostname on this machine not fully qualified?
The host is fully qualified.
> By default, Cyrus appends the fully qualified hostname to the userid
> when looking up the secret in sasldb2.  If you have a mismatch in
> realms, it won't find the secret.