tadeck / yubico-yubiserve

Automatically exported from code.google.com/p/yubico-yubiserve
GNU General Public License v3.0
0 stars 0 forks source link

When adding a new key, the key is not active. #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Add a new key (using sqlite database)
2. Send a query to the server

What is the expected output? What do you see instead?
otp=rcje9u30rnr862234503
status=BAD_OTP
t=2011-01-05T11:20:43

What version of the product are you using? On what operating system?
version 3.0

Please provide any additional information below.
Issue reported by huangmingyou.

Original issue reported on code.google.com by b1ga...@gmail.com on 5 Jan 2011 at 1:59

GoogleCodeExporter commented 9 years ago
So, after adding a new key, you have to set active=1 to that key (and after 
that, it works)?

Original comment by b1ga...@gmail.com on 5 Jan 2011 at 2:00

GoogleCodeExporter commented 9 years ago
this version is svn revision 37. last change at 2010-12-14. OS is ubuntu 10.04 
server.

1. when add a new key in mysql . the key is not enable by default.
2. when use sqlite database,  verifiy will false ,and report BAD_OTP, and I 
found the sqlite database had not update the connter;

Original comment by huangmingyou on 6 Jan 2011 at 8:35

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I have got the same issue, please advise.

Original comment by i...@vircon.nl on 3 Feb 2011 at 2:09

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Okay, working on it :)

Original comment by b1ga...@gmail.com on 3 Feb 2011 at 4:41

GoogleCodeExporter commented 9 years ago

Original comment by i...@vircon.nl on 24 Mar 2011 at 11:21