Fix: Support CKAN 2.11.x Config apitoken_header_name - default to 'Authorization' #245
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
duttonw
changed the title
duttonw
changed the title
duttonw
approved these changes
Mar 3, 2025
This was referenced Mar 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds support for the new "apitoken_header_name" CKAN Config, in which you can specify alternative header for CKAN API Tokens.
This is an issue, when your CKAN instances are under Basic HTTP Authentication, which breaks the default "Authorization" header and as a result, uploading doesn't work and return 403 HTTP.
Those changes make sure that Xloader takes into account the changed Header for accepting CKAN API Keys.