afs commented on issue #1292: URL: https://github.com/apache/jena/issues/1292#issuecomment-1126020705
The application sees a failed authentication as an exception 401. Fixes and improvements in #1301. HTTP authentication is a bit squirly because of legacy cases. Adding challenge handling for bearer auth is probably doable but it's yet another step. Rather than delay everything PR #1301 at least fixes the original problems and should work when the bearer token is added - failure is a 401 exception. One case is that the token is being passed along a path service requests and code in the 401 handler may find it hard to give transparent. PR #1301 at least fixes the original problems and should work when the bearer token is added. @seebi -- I'm guessing that in your architecture, the token is added before the original request and not based on a HTTP challenge. Is that correct? Testing the PR would be great - this is quite sensitive to the execution environment (and my reading of the RFCs!). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
