Storing passwords as plain text is remedied in this scenario by wrapping the password in a MD5(), SHA1(), SHA2(), etc. or your own code inspired. You’ll notice that the password field was set as a 32 character VARCHAR. This is really intended to store passwords as MD5 hashes. However, for this example, I didn’t want to get hung up in an encryption “yack-shave” to mask the intent of using a ACID layer API to remove expiring tokens at a policy level.

I’ll add to the requirements at the top of this document so the intent is more clear. Thanks!

I see some security issues with this code. You should not be using the password or username as components in the token generation. Tokens should be purely random. Also, you should not be storing passwords in plain text at the database level. I recommend, at a minimum, attaching a random salt value (different for each user) and then using a strong hashing function such as sha256. Iterative hashing of the password would be even better.

I have to modify “configure” to add the -m64 to compile sysbench as 64bit.

otherwise, I got the following error:

gcc -D_THREAD_SAFE -g -O2 -o sysbench sysbench.o sb_timer.o sb_options.o sb_logger.o db_driver.o tests/fileio/libsbfileio.a tests/threads/libsbthreads.a tests/memory/libsbmemory.a tests/cpu/libsbcpu.a tests/oltp/libsboltp.a tests/mutex/libsbmutex.a drivers/mysql/libsbmysql.a -L/usr/local/mysql/lib -lmysqlclient_r -lm
ld: warning in /usr/local/mysql/lib/libmysqlclient_r.dylib, file is not of required architecture
Undefined symbols:
“_mysql_store_result”, referenced from:
_mysql_drv_describe in libsbmysql.a(libsbmysql_a-drv_mysql.o)
_mysql_drv_store_results in libsbmysql.a(libsbmysql_a-drv_mysql.o)

gli-mn:sysbench-0.4.12 root# file /usr/local/mysql/lib/libmysqlclient_r.dylib
/usr/local/mysql/lib/libmysqlclient_r.dylib: Mach-O 64-bit dynamically linked shared library x86_64
gli-mn:sysbench-0.4.12 root#

Daylight savings doesn’t really factor in, because the key won’t change based on user timezone preference. That part will be application dependent to pick a date_key that fits the ETL job for the fact data creation.