-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP digest authentication against remote SPARQL endpoint broken when using latest AuthLib approach (jena-arq) #1233
Comments
It is wrong - I'll added some tests for digest auth that are missing. Please do submit a PR. |
PR ready. I would be happy to make the update also for the 4.3.2 release (which I am currently using). To do this do you need to create first a relevant branch in the jena repo? |
The project works on a release tick cycle - release every 3-4 months. We have a finite amount of people time. So the community has to decide what they want. Bug fix releases would mean less elsewhere. We have settled on the regular (every 3-4 months) releases and use @deprecated to signal changes rather than run multiple development release branches. Jena isn't in a state of large-scale changes. 4.3.1 was important because it updates to log4j 2.16.0 and the log4j security issues. Jena 4.4.0 further updates to log4j 2.17.1. You should be able to use Jena 4.4.0 (and Jena 4.5.0). The fix is now in the code base and the next run of snapshot builds (I've just kicked off a build) will put the development snapshots into: https://repository.apache.org/content/groups/snapshots/org/apache/jena/ |
Thanks @afs . I accept your point on multiple development branches and will plan an upgrade to the latest version. |
Tests for digest auth added. |
When switching to the latest approach to authenticate against a remote SPARQL endpoint using digest authentication I noticed that authentication no longer worked.
Looking into the jena-arq code the problem seems to be with class org.apache.jena.http.auth.AuthLib and specifically method handle401(). In here, when method DigestLib.buildDigest() is called, the request method and request target parameters seem to be passed in inverse order. Doing a simple debug on my end and switching these values around seems to resolve the issue.
Could you please confirm on your end? If yes, then I would be happy to submit a PR that resolves this.
The text was updated successfully, but these errors were encountered: