cloudfoundry / cloudfoundry/stratos
Handle UAAs/CFs with lagging date
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Issue seen locally using an old pcfdev where server time lagged by multiple days
UAA/Stratos - session cookie served had an expiration time that was already exceeded
- front end logged in service checks cookie, sees expired time & fetches new cookie
- new cookie has expired, fetch another, etc
CF/Jetstream - the cf auth token has a similar issue
- jetstream proxied requests have to make additional calls per request (? call one fails, call two to fetch new token & call three to retry original call ?)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the UAA/Stratos session-cookie handling and the CF/Jetstream auth-token flow, reproducing the behavior with a server clock several days behind. Done means expired credentials no longer cause repeated cookie refreshes or unnecessary proxied request calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- api, authentication, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100