FI-3219 Add access token outputs #9
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
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.
Summary
Currently, the UDAP token exchange tests have an output for the entire JSON response body from the token exchange, and tests interested in using any of the values from the response must re-parse the entire response body.
This PR updates tests to use specific outputs for access token, received scopes, and expiration time for easier use by downstream tests. I also did some minor changes to the existing input names to be fully consistent with the input refactor done in a previous PR.
Testing Guidance
None - unit tests are not impacted, and we do not have a reference implementation to test against that would visualize the outputs in the web app.