Bump ckanext-auth; Add JWT token generation back in #68
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
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 bumps ckanext-auth to a custom branch that provides a user API token in the login response (required for frontend CRUD operations).
Note: I have to add back in the auto-generation of JWT tokens in the Dockerfiles. API token generation does not work properly without the JWT tokens being set up.
When reviewing this, please also review the code living in a custom branch in ckanext-auth (it may or may not end up in a PR for the ckanext-auth CKAN 2.10 branch eventually, but for now, we're not merging). Here's the commit for these changes datopian/ckanext-auth@303ffc1