Fix parsing of access_token
key from response JSON for OAUTH2
#216
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.
when using
OAUTH2
as STORAGE_API with use of credentials such asclient_id
,client_secret
etc,access_token
is first fetched and further requests use fetched token to perform request until it expires.regex used to parse response and get
access_token
had an extra trailing space, which is not present in response causing amanda to not parse it hence sending emptyaccess_token
i.eAuthorization : Bearer (null)
.this fixes parsing, further enables users using
OAUTH2
as authentication mechanism.fixes #214.
Changes:
Fix regex's parsing response to get valid set of credentials
Testing Changes.
account of no or more trailing space in regex's
make setting HTTP requests to 1.1 if user wishes to, by allowing settings another configuration in .conf