Bugfix/SK-737 | Conflict in auth metadata in grpc client #554
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.
authorization metadata with token was added both by the metadata plugin as well as manually in each grpc stub call.
A secure channel must be used to make use of token authentication. If one would like to use an insecure channel (without TLS/SSL) but still have token authentication, then one has to modify the client and use self._add_grpc_metadata("authorization", self.token)