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.

Sign up for GitHub

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

Jump to bottom

Add a refresh token to the RPT #238

Closed
xmlgrrl opened this issue Jan 27, 2016 · 1 comment
Closed

Add a refresh token to the RPT #238

xmlgrrl opened this issue Jan 27, 2016 · 1 comment
Labels
core Related to (original UMA1) core spec scope; may use obsolete language simplify Related to the UMA1-to-UMA2 effort to simplify UMA V2.0

Comments

@xmlgrrl
Copy link

xmlgrrl commented Jan 27, 2016

Although I believe this notion is mentioned incidentally in the larger issues of #153 and #154, I wanted to mention it here so that the issue could be considered no matter the fates of the others.
@xmlgrrl xmlgrrl added the core Related to (original UMA1) core spec scope; may use obsolete language label Jan 27, 2016
@xmlgrrl xmlgrrl added the simplify Related to the UMA1-to-UMA2 effort to simplify UMA label Feb 4, 2016
@xmlgrrl xmlgrrl added the V2.0 label Sep 30, 2016
@xmlgrrl
Copy link
Author

xmlgrrl commented Jan 2, 2017

We do allow a refresh token. An RPT is an OAuth access token (confirmed/discussed in UMA telecon 2016-08-18: http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2016-08-18).

@xmlgrrl xmlgrrl closed this as completed Jan 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core Related to (original UMA1) core spec scope; may use obsolete language simplify Related to the UMA1-to-UMA2 effort to simplify UMA V2.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xmlgrrl