Correctly add authorization header to Subscription.channel.header #14
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
Previously, when the Subscription Server tests tried to add a Subscription.channel.header value with a bearer token, it did so at the Subscription level instead. Now it does so correctly.
Testing Guidance
Run the Server tests agains the client tests following the instructions - see suite instructions - but removing the
"header": ["Authorization: Bearer SAMPLE_TOKEN"],
row from the Workflow Subscription Resource input on the server tests. Verify that the tests run correctly and that when viewing the client test responsible for verifying the Subscription creation (1.3.01 - Client Subscription Conformance Verification) that the Subscription creation request includes that content under Subscription.channel.