For ODS, the dba user must import a certificate with primary key and with name
The process takes the following steps:
- A signing authority (e.g., RSA Labs) generates a site certificate.
- The site certificate is used to generate certificates for ODS users.
- The site certificate is imported with name id_rsa for user
dbausing the Conductor.
- As a result, the ODS user certificates can be authenticated against the site certificate.
If there is a service that requires a different key, the Conductor can be used to import another certificate for the relevant user.
You can use a Key from a global signing authority or produce a self-signed key using the ODS Identity Manager.
Details and more information how to generate the key you can find here.
- Setting up PubSubHub in ODS
- PubSubHubBub Demo Client Example
- Feed subscription via PubSubHub protocol Example
- Setting Up PubSubHub to use WebID Protocol or IP based control lists
- Creating and Using a SPARQL-SSL based Endpoint
- Set WebID Protocol ACLs using the Virtuoso Authentication Server UI
- WebID Protocol ACLs Tutorial
- SPARQL OAuth Tutorial
- WebID Protocol Support in OpenLink Data Spaces?
- Guide to Setting up a X.509 certificate issuer and HTTPS listener and Generating ODS user certificates
- Generate an X.509 Certificate hosted WebID Guide
- ODS Briefcase WebID Protocol Share File Guide
- WebID Protocol Specification
- Test WebID Protocol Certificate page
- WebID Protocol Certificate Generation page
- Virtuoso Demo SPARQL-SSL Endpoint