Matthias Hanel fa12d096cd Fix jwt based user/activation token revocation and revocation granularity ...

user and activation token did not honor the jwt value for all * on
connect.

activation token where not re evaluated when the export revoked a key.
In part this is a consistency measure so servers that already have an
account and servers that don't behave the same way.

in jwt activation token revocations are stored per export.
The server stored them per account, thus effectively merging
revocations. Now they are stored per export inside the server too.

fixes nats-io/nsc/issues/442

Signed-off-by: Matthias Hanel <mh@synadia.com>

2022-01-25 13:48:12 -05:00

4.8 KiB

Raw Blame History

View Raw