JWT expiry is 30seconds
Type
-
Feature Request -
Bug Report
Priority
-
High -
Medium -
Low
Bug Report
Breaking
-
YES -
NO
Attached Logs?
-
YES -
NO
Current behavior
As a part of the integration tests, the Notification service sends a JWT token with an expiry window of 30 seconds. This request is received by the Register service as it is mimicking a subscriber.
The 30 seconding expiry window is making the behavior flaky. Most requests are getting rejected.
Expected behavior
What is the motivation to keep it 30 seconds? Can we keep the expiry window configurable and manage it through application properties?
Steps to reproduce
Integration tests can be run multiple times.