cloudfoundry / cloudfoundry/uaa-release
In mid 2018 is the default "refreshTokenFormat":"jwt", "refreshTokenUnique":false the best approach?
Open
Nobody has claimed this yet.
unscheduled
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 77
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 14
Description
- https://www.pivotaltracker.com/n/projects/997278/stories/140368609
- https://github.com/cloudfoundry/uaa-release/commit/a717b527de6de180b8b8c7b5c82b99174da524e3
- thread from slack that discusses this topic too in passing https://cloudfoundry.slack.com/archives/C03FXANBV/p1520476843000067
This story seems to chronologically pre-date cf-deployment. Is it still the best thing for everyone to use JWT and "refreshTokenUnique":false by default?
Contributor guide
No contributing guide indexed for this repository
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
Review the linked Pivotal Tracker story, uaa-release commit a717b527de6de180b8b8c7b5c82b99174da524e3, and referenced Slack thread. Compare the historical rationale for refreshTokenFormat=jwt and refreshTokenUnique=false with current cf-deployment usage, then establish whether a default change is warranted and record the decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100