In mid 2018 is the default "refreshTokenFormat":"jwt", "refreshTokenUnique":false the best approach? #93
Labels
Comments
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/158815154 The labels on this github issue will be updated when the story is started. |
strehle
added a commit
to cloudfoundry/uaa
that referenced
this issue
Jul 17, 2023
Default should be opaque, at least the default. History about cloudfoundry/uaa-release#93 Some tests rely on JWT for refresh, therefore added for these tests again jwt.token.refresh.format=jwt
|
No expected work needed to e done in regards to the Founcation Infrastructure Working Group association. |
strehle
added a commit
to cloudfoundry/uaa
that referenced
this issue
Jul 27, 2023
* Change default of refresh token format Default should be opaque, at least the default. History about cloudfoundry/uaa-release#93 Some tests rely on JWT for refresh, therefore added for these tests again jwt.token.refresh.format=jwt * more default changes * more default changes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This story seems to chronologically pre-date cf-deployment. Is it still the best thing for everyone to use JWT and
"refreshTokenUnique":falseby default?The text was updated successfully, but these errors were encountered: