-
Notifications
You must be signed in to change notification settings - Fork 19
WebID certificate
In order to be able to access protected resources you need to use a WebID enabled X509 Certificate.
When using curl
on your localhost server you need to use the test-localhost.pem
certificate with the test
password. You can do that by using the --cert eg/test-localhost.pem:test
flag.
If you want to use your own certificate then just point curl using the --cert
flag to your certificate with the corresponding password.
You can install the certificate in the eg
directory into your browser or keychain.
Open the eg
directory with
$ open eg/
This will open a file explorer. You can the double click on one of the certificates
which will import it into your Keychain.app
.
You can the try your https://localhost:8443/2013/ server, which will ask you for a certificate when you need one.
- Open the Preferences Dialog box
- Click the
Certificates
tab - Click the
View Certificates
tab - Make sure the `Your Certificates tab is selected
- Click the
import
button at the bottom - Select the
test-localhost
certificate
Creating a WebID certificate from your browser is much easier. (It can be easier than this, but that is still a todo)
After starting your server you can point your browser to http://localhost:9000/srv/certgen or to the service over https and create yourself a certificate. For testing purposes and in order to be able to work without the need for network connectivity use `http://localhost:8443/2013/cert#me'. The WebID Certificate will be signed by the agent with Distinguished Name "CN=WebID,O=∅" and added by your browser to its keychain.
( Todo: later we will add functionality to add create a local webid that also published the RDF ) To make the WebID valid you will need to publish the relavant rdf at that document location as explained in the WebID spec