I was able to reproduce this with both UUID and PKI tokens against a mysql:// sqlalchemy connection string and explicitly setting the token driver to the sql-based one (which is not the default). This bug appears to affect v3 auth, but not v2 auth.
I was able to reproduce this with both UUID and PKI tokens against a mysql:// sqlalchemy connection string and explicitly setting the token driver to the sql-based one (which is not the default). This bug appears to affect v3 auth, but not v2 auth.