Closed vadimasg closed 2 years ago
Hi, the library does not handle these scenarios: SPARQL queries are just sent to the endpoints, which are supposed to be freely accessible (e.g.: dbpedia, ...). Did you mean you would expect at least basic authentication scenarios to be fullfilled? (e.g: I would need ability to pass custom headers to the SPARQL request, in order to be authorized through the bearer token I provided).
Regards, Marco
Hi, Yes, we need basic authentication through custom header on our GraphDB endpoint (token or user/password). Thank you for a quick response!
Regards, Vadimas
Hi Vadimas, I committed a change to address the need for specifying an Authorization header with "Basic XXX" or "Bearer XXX" values to be sent within the request to SPARQL/SPARQL Update endpoints.
I kindly ask you to compile master branch of the library and tell me if this works for your needs on GraphDB. You have to call one of the 2 new methods SetBasicAuthorizationHeader or SetBearerAuthorizationHeader on your RDFSPARQLEndpoint instance before applying the SPARQL query.
I'm not sure about the most common or proper way of encoding the header secret, so I assume it's up to the application's responsibility to provide a value which has already been encoded (ISO-8859-1, UTF8, ...)
Regards, Marco
Thank you Marco, I'll give it a try and definitely let you know!
Regards, Vadimas
Hi Vadimas, were you able to verify the feature? Did GraphDB accept the SPARQL query when sent with the new Authorization header?
Regards, Marco
Hi Marco,
Yes, SetBasicAuthorizationHeader works perfectly well, thank you! Will investigate your package further.
Thank you, Vadimas
On Sat, Jun 25, 2022 at 7:46 AM Marco De Salvo @.***> wrote:
Hi Vadimas, were you able to verify the feature? Did OntoGraph accept the SPARQL query when sent with the new Authorization header?
Regards, Marco
— Reply to this email directly, view it on GitHub https://github.com/mdesalvo/RDFSharp/issues/263#issuecomment-1166265254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AY2HODY5EHSAGL7OJPFITKLVQ3WRJANCNFSM5YX4BOJQ . You are receiving this because you authored the thread.Message ID: @.***>
-- [image: photo-logo] https://img.newoldstamp.com/r/525173/p Vadimas Geguzinskis Backend Developer
web: helpseeker.co https://img.newoldstamp.com/r/525173/w email: @.***
[image: facebook] https://img.newoldstamp.com/r/525173/facebook [image: twitter] https://img.newoldstamp.com/r/525173/twitter [image: linkedin] https://img.newoldstamp.com/r/525173/linkedin [image: instagram] https://img.newoldstamp.com/r/525173/instagram [image: banner] https://img.newoldstamp.com/r/525173/b In the spirit of Reconciliation, we acknowledge living on the traditional territories of the Blackfoot Confederacy (Siksika, Kainai, Piikani), the Tsuut’ina, the Îyâxe Nakoda Nations, the Métis Nation (Region 3), and all people who make their homes in the Treaty 7 region of Southern Alberta. [image: Promotional] https://img.newoldstamp.com/r/525173/6
Glad to hear this. I'll publish the version containing this feature in August. In the meanwhile feel free to contact me for any doubts or issues.
Regards, Marco
Does the package support auhentication/authorization for endpoints?