Fix issue 1592 (Online tests can no longer be run with a service account) - #1593
Merged
Conversation
the human user credintials CONTRIBUTING.md is updated with instructions on how to obtain these human user credintials (an authorized_user.json file) This fixes the issue burnash#1592
Service Account cridentials and OAuth user credentions with the refernce to the procedure in the docs/oauth2.rst docs/oauth2.rst is updated to reflect the current (and more detailed) procedure to obtain OAuth user credentials
Contributor
Author
|
@antoineeripret , I have implemented the changes, as we discussed in the issue. I also slightly updated the relevant section of the |
This was referenced Jul 31, 2026
This file contains hidden or 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
2 participants
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.
Test code is updated to allow the test suite to authenticate using human user credintials
CONTRIBUTING.md is updated with instructions on how to obtain these human user credintials (an authorized_user.json file)
This fixes the issue #1592