Skip to content
This repository has been archived by the owner on Dec 29, 2020. It is now read-only.

Refresh tokens and expiry do not need to be tied together #24

Open
samskiter opened this issue Oct 30, 2014 · 0 comments · May be fixed by #30
Open

Refresh tokens and expiry do not need to be tied together #24

samskiter opened this issue Oct 30, 2014 · 0 comments · May be fixed by #30

Comments

@samskiter
Copy link

The OAuth2 spec makes no connection between refresh tokens and expiry. It's possible to have one without the other. Specifically - section 4.4 says there SHOULD NOT be a refresh token. While it is rare that iOS applications will make use of this form of auth, I propose to relax the constraints on refresh tokens and expiry
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

decouple refreshToken and expiration properties. ryanmaxwell/GROAuth2SessionManager
1 participant
@samskiter