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

Update PKCE usage requirements and errors #239

Merged
merged 2 commits into from
May 29, 2019
Merged

Update PKCE usage requirements and errors #239

merged 2 commits into from
May 29, 2019

Conversation

lbalmaceda
Copy link
Contributor

Changes

The current requirements state that the application should be of type "native". Normally that's enough, but some users had the token endpoint authentication method set to other than "none", making the whole flow fail.
This PR attempts to prevent this by clarifying that both settings should have a given value for PKCE to work.

Testing

  • This change adds unit test coverage

  • This change adds integration test coverage

  • This change has been tested on the latest version of the platform/language or why not

Checklist

@lbalmaceda lbalmaceda added the tiny Tiny review label May 28, 2019
@lbalmaceda lbalmaceda added this to the v1-Next milestone May 28, 2019
@lbalmaceda lbalmaceda requested a review from a team May 28, 2019 17:15
@joshcanhelp joshcanhelp requested review from joshcanhelp and removed request for a team May 28, 2019 18:16
README.md Outdated Show resolved Hide resolved
auth0/src/main/java/com/auth0/android/provider/PKCE.java Outdated Show resolved Hide resolved
@damieng damieng merged commit 829cc32 into master May 29, 2019
@damieng damieng deleted the update-pkce-rer branch May 29, 2019 14:20
@lbalmaceda lbalmaceda modified the milestones: v1-Next, 1.16.0 Jun 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants