Revocation events catching too many tokens

[Adam Young]

We've seen an effect where setting the dfefault token handler to Fenet, and depending on Revocation events breaks several tests. These tests are supposed to track that a tokne comes back as invalid. However, what actually happens is the admin users token is invalid, returning a 401 instead of a 404.

Putting a 1 second delay between, for example, the delete role assignment event and the token validation causese the validation to properly return the 404.

It looks like the revocation tree is somehow matching the admin token in its check.

[sandeep nandal (nandal)]

Hi Adam,

could you write down the steps to reproduce and the version you use to explain it further.

[Dolph Mathews (dolph)]

It's hard to know if this is still an issue without any steps to reproduce.