Hello,
I’m here again
I have set up a policy where otppin=1 but when I try to authenticate with https://localhost:5001/auth/index
I cannot manage to login.
If I set otppin=0 or otppin=2 everything goes perfectly and I am able to
authenticate.
Inside my test db the password is stored as plain-text, is this right or
have I to encode it with md5 or something else?
PS: when I’m logging in I wrote:
user: paolo
password: plainpwdOTPVALUE
Kind regards
CorneliusAm Dienstag, 14. Oktober 2014 12:23:02 UTC+2 schrieb Paolo:
Hello,
I’m here again
I have set up a policy where otppin=1 but when I try to authenticate with https://localhost:5001/auth/index I cannot manage to login.
If I set otppin=0 or otppin=2 everything goes perfectly and I am able to
authenticate.
Inside my test db the password is stored as plain-text, is this right or
have I to encode it with md5 or something else?
PS: when I’m logging in I wrote:
user: paolo
password: plainpwdOTPVALUE
Works perfectly thanks a lot!
I will write an how to on my blog about this ;)On Tuesday, October 14, 2014 12:48:15 PM UTC+2, corneliu…@netknights.it wrote:
Am Dienstag, 14. Oktober 2014 12:23:02 UTC+2 schrieb Paolo:
Hello,
I’m here again
I have set up a policy where otppin=1 but when I try to authenticate
with https://localhost:5001/auth/index I cannot manage to login.
If I set otppin=0 or otppin=2 everything goes perfectly and I am able to
authenticate.
Inside my test db the password is stored as plain-text, is this right or
have I to encode it with md5 or something else?
PS: when I’m logging in I wrote:
user: paolo
password: plainpwdOTPVALUE