Configuring HTTPS Endpoints in Virtuoso
Virtuoso HTTPS Endpoints can be configured through the Virtuoso Conductor or by manually editing the Virtuoso configuration file.
The Certificate and Public Key upon which the SSL connections depend may be hosted within Virtuoso, or in the local File System. Note that if you want to change where the Certificate and Public Key are hosted (i.e., from Virtuoso to the File System, or vice versa), the Endpoint Listener should be stopped before the configuration is adjusted.
The instructions below presume that if you're manually editing the configuration file, you want to host the Certificate and Public Key in the filesystem. Likewise, if you're configuring the endpoint through the Conductor, it is assumed that you want to host the Certificate and Public Key within Virtuoso.
- Configuring HTTPS Endpoints through the Virtuoso Conductor
- Configuring HTTPS Endpoints by manually editing the configuration file
Related
- 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
- 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
- CA Keys Import using Conductor
- 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
