Closed SaschaAdler closed 3 years ago
I have observed Swift giving a 401 within the time period already. Seems that there are a variety of reasons why Swift will request authentication, so assuming it is based in time will periodically fail.
Will the sapindale tools do this on the client side when interacting with Couch via Upholstery? I'm wondering if it is worth having the error page output something other than the "JWT authenication failure" (Yes, spelling mistake :-) page which may be useful for developers, but not for any regular humans that might see it.
An FYI that when trying to do a large request with https://admin-demo.canadiana.ca/archivalmanifest that the adding of new requests stopped when the token expired. Having the token auto-renew would be great!
https://crkn-rcdr.slack.com/archives/CAXMM3JTW/p1591390327147200
This can work one of two ways:
The second option seems more complicated, but allows for sapindale to not guess at the length the interval before fetching a new token should be.
Of course, if amsa requires a new login, the new fetch will fail, and this will have to be handled effectively.