Cookie expiration is not in sync with IMS token expiration
Open
da-ue
enhancement
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 3
- Avg merge
- 18h
- Merged PRs (30d)
- 15
Description
Today it can happen the IMS token is expired but the cookie is still valid as we set if for 1day. But the time it is created the IMS token can already be close to expiration.
Contributor guide
Research direction
The issue names the IMS token and the cookie expiration but no files or tests. Start by tracing where the IMS token and one-day cookie are created, then compare their expiration values when the token is already near expiry. Done means the cookie no longer remains valid beyond the IMS token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100