fix!: The term "scheme" is used properly as defined by RFC9110 #1042
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.
Related issue(s)
closes #1044
Checklist
Description
As described in the issue referenced above, a property allowing to configure the Authorization header scheme is named
schema
(a at the end). This is unexpected and given the currently raised JSON schema validation error on start of heimdall not obvious. Because of that this PR changes the name of the property to what everybody expects it to be, namelyscheme
.NOTE: Affected are all authenticator mechanisms, which define a property of
Authentication Data Source
type, namely (jwt
,oauth2_interospection
andgeneric
).The below
jwt
authenticator examples show the differences between the configuration before this PR and configuration changes introduced by this PR.old configuration
new configuration