Added Web Token library. #46
Conversation
There was a problem hiding this comment.
It is assumed the redis server is running somewhere already? I didn't see a 'lookup' step or anything from the Jedis code.
Operationally, having redis available is probably much easier in k8s. I guess we should talk about this will the ops group and see what they think.
|
|
||
| private final String accessToken; | ||
| private final String refreshToken; | ||
| private final long expiryTimeMilliseconds; |
There was a problem hiding this comment.
I wonder if the subject and issuer (sub & iss) would be useful to have here for debugging or logging purposes.
|
This library will assume a Cache is running. We supply a client for Redis using the |
|
Ah, I see, thanks. |
No description provided.