Add test case for validating WWW-Authorization header when invocating an API with API Keys using invalid Authorization header #13523
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.
Purpose
As identified by [1], the WWW-Authorization response header contains null for an API with API-Key enabled. This PR introduces a test case to validate the WWW-Authorization header to validate the presence of the appropriate content.
Implementation
Introduce a new test case which checks if the WWW-Authorization header contains the string
"API Key realm=\"WSO2 API Manager\""
.The validation is done under 2 possibilities,
[1] - wso2/api-manager#3062