Modifies folio_api to use folioAccessToken in cookie headers. #5
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.
Please describe the problem you'd like to be solved:
In the upcoming Sunflower Release of FOLIO, non-expiring tokens will no longer be supported. (RTR docs). The authentication method authn/login will be removed from the login module.
Describe the solution you'd like to see implemented:
I believe there will be a lot of libraries needing to update their current folio-spineomatic middleware solution to be able to support token retrieval from the current authentication method authn/login-with-expiry
Describe alternatives you've considered:
Since a request for the XML of an item only happens when a barcode is scanned, updating the codebase to authenticate at authn/login-with-expiry for each request should suffice. This is suggested in the documentation for refresh token rotation underneath the section titled:
"A guide for non-module clients such as scripts or other integrations".
Token retrieval from set-cookie response headers will also need to be implemented since tokens no longer will be sent in the response body.
Additional context:
FOLIO Release Cycle