Open sberyozkin opened 3 years ago
Any movement on this? This is literally the only code we have that isn't reactive or coroutines. We verify our JWTs using HTTP JWKs which obviously required remote fetches. The fetches are already reactive this interface is the only limiter.
We should have a new module which will offer
Uni
responses forJWTParser
andJWTCallerPrincipalFactory
which will help Quarkus users write better reactive applications involving smallrye-jwt