Get an account
This guide describes how to get access to an application.
Are you in? Then take a look at the UI overview and the get started guide.
Get WebID
LinkedDataHub uses WebID as the Single sign-on (SSO) protocol for distributed applications, which is based on authentication using TLS client certficates. Using WebID, you will be able to authenticate with every LinkedDataHub application. Read more about WebID.
Unlike most LinkedDataHub resources, your WebID profile will have public access as required by the protocol. Your email address will be hidden however.
If you have completed the setup and own an instance of LinkedDataHub, ssl/owner/keystore.p12 file is your WebID certificate. Password is the $owner_cert_pwd value you supplied ./scripts/setup.sh file.
ssl/owner/cert.pem is the PEM version of the certificate, for use with the command line interface.
Install certificate
The final step is to install the client certificate into your web browser. It is done by importing the .p12 file using the browser's certificate manager and providing the password that you supplied during signup. The manager dialog can be opened following the steps below, depending on which browser you use:
- Google Chrome
- Settings > Advanced > Manage Certificates > Import...
- Mozilla Firefox
- Options > Privacy & Security > View Certificates... > Import...
- Apple Safari
- The file is installed directly into the operating system. Open the file and import it using the Keychain Access tool.
- Microsoft Edge
- Does not support certificate management, you need to install the file into Windows. Read more here.
You need to install the certificate on all devices/browsers that you are using to access LinkedDataHub.
Log in
With the certificate installed, there is no login procedure — you are automatically authenticated on all LinkedDataHub applications. This is known as Single sign-on (SSO).
Applications can provide public access to some or all documents, meaning you can freely browse their public resources and perform actions that are allowed for public access. In order to access protected (non-public) resources, as well as to access administration application, users have to be authenticated as well authorized (authorizations can be requested).
Authenticated agents are not guaranteed to have access to all resources. Different access levels for different agents can be specified by the application administrators.