add authentication scheme argument to be possible to use bearer #52
Conversation
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
1 participant
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.
Rationale
Let us know why do you make a change
This change could be important to give access to authenticate the API from Corva without a Api Key, I will be possible to use Bearer authentication scheme that is accessible to developers authenticated.
Changes
Describe what you changed
I add a new argument at the constructor of Api to be possible to choice the authentication scheme that the developer would like to use. The argument will keep working for old version due to the default value for authentication_scheme
[JIRA ticket](put the link to the corresponding JIRA ticket here)
TODO