Validate TokenResponse #341
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 9456aed.
rajdeepnanua-okta
force-pushed
the
rn_validateTokenResponse
branch
from
cc053e4 to
80b3b36
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR validates TokenResponse for required parameters before returning the TokenResponse. Otherwise, an AuthorizationException is thrown. access_token, token_type, and expires_in are all required parameters in okta-mobile-kotlin, and so those are the parameters being validated.
Also, reverted an earlier README update which was redundant due to existing proguard-rules.pro in the SDK.
Testing details:
Other considerations:
RESOLVES:
OKTA-XXXXX
Primary Reviewer(s):
Additional Reviewers:
Security Reviewer(s) (@ okta/rex-team if necessary):
UX Reviewer(s) (if necessary):