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

PKCE vs non-PKCE authorization flow and refresh token limitations #98

Open
MeditoDiTerra opened this issue Jan 30, 2023 · 0 comments
Open

Comments

@MeditoDiTerra
Copy link

Hello,

I'd like to know, if deliberately not using PKCE in a mobile app intended for public release is still ok?

I have successfully implemented both methods, was fully committed to go for PKCE until I found out the refresh token can only be used once, after which the whole authorization process has to be repeated.

Non-PKCE auth flow, on the other hand, does not suffer from this limitation. I assume the PKCE requirement is for added security, but from the UX perspective, I definitely prefer not to bother users with constant authorization requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant