Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the permission ticket optional when "upgrading" the RPT for an UMA-native refresh flow #353

Open
xmlgrrl opened this issue Aug 24, 2017 · 0 comments
Labels
extension Idea that may be suitable for an extension spec or UMA Request For Enhancement grant Related to UMA2 Grant

Comments

@xmlgrrl
Copy link

xmlgrrl commented Aug 24, 2017

James brought up the idea of a kind of client-to-AS-first UMA-native refresh flow, where no policy context is needed, came up in UMA telecon 2017-08-23, but we didn't have time to consider it fully at this stage in V2.0.

We did discuss our original motivation for wanting to ensure that a regular old OAuth refresh token and refresh flow "just works" as expected, and we made some decisions in this call confirming how that should go.

@xmlgrrl xmlgrrl added extension Idea that may be suitable for an extension spec or UMA Request For Enhancement grant Related to UMA2 Grant labels Aug 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extension Idea that may be suitable for an extension spec or UMA Request For Enhancement grant Related to UMA2 Grant
Projects
None yet
Development

No branches or pull requests

1 participant