Replies: 1 comment
-
I think that makes a lot of sense. Fwiw if you have the bandwidth to actually contribute this feature back to the open-source project, it might even be something you could just add into the existing SPARQLRepository class, instead of extending it. The main thing is to have these properties used when configuring the HttpClient used internally. You'll want these properties used to configure a Edit: you could possibly also manually set your authorization header I guess. In that case you wouldn't need to use a CredentialsProvider but could instead just use the |
Beta Was this translation helpful? Give feedback.
-
Hi,
I'm currently working with an RDF store that uses an Authorization Header (similar to JWT or OAuth) for security. I'm looking to architect a means by which a user can leverage the RDF4j Console to access this store. After initial investigation, I think it would make the most sense to extend the SPARQLRepository class/type and create a new custom repository type. This way users can use a similar SPARQLRepository template structure when defining access to the RDF store. The new class would include parameters for API keys/tokens.
Example (note the repositoryType and added custom fields):
Looking for suggestions on how I would go about adding this functionality. Or are there extensions that already exist to allow for this?
Beta Was this translation helpful? Give feedback.
All reactions