You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are in the process of migrating our application from Micronaut 3.7.0 to 4.x.
Our application is running in K8 environment with 500m cpu. While testing we are intermittently facing Read Timeout while loading JWK for JWT signature validation.
As per this issue 1633, if the client and server share the same event loop and the event loop deadlocks if a blocking operation is performed.
This PR added reactive API for JWKS. Does any other specific configuration is required.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are in the process of migrating our application from Micronaut 3.7.0 to 4.x.
Our application is running in K8 environment with 500m cpu. While testing we are intermittently facing Read Timeout while loading JWK for JWT signature validation.
As per this issue 1633, if the client and server share the same event loop and the event loop deadlocks if a blocking operation is performed.
This PR added reactive API for JWKS. Does any other specific configuration is required.
Micronaut Core - 4.7.5
Micronaut security - 4.11.1
Micronaut security jwt - 4.11.1
My Current Configuration..
Beta Was this translation helpful? Give feedback.
All reactions