a ; ; "2026-06-16T20:34:21.352Z"^^; ; "How to get login to LinkedDataHub"; "Get an account"; ; . a ; ; "signup.png"; "signup.png"; "cf383c52ac014823a2627b055cca06b21d8fe8b0" . a ; "
\n

This guide describes how to login to LinkedDataHub.

\n
\n
\n

In order to authenticate as the owner of a LinkedDataHub instance, you need to use the WebID authentication method.

\n
\n
\n \n
\n
\n
\n

Get certificate

\n

LinkedDataHub uses WebID as the Single sign-on (SSO)\n 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.\n Read more about WebID.

\n

There are two ways to get a LinkedDataHub WebID: setup and signup.

\n
\n \n
\n
\n

Complete the setup and run own an instance of LinkedDataHub.

\n

The ssl/owner/keystore.p12 file is your WebID certificate. The password is the owner_cert_password Docker secret value.

\n
\n
\n

Sign up to an existing instance of LinkedDataHub. Click the Sign up button and fill out the form with your\n details to get a WebID, as shown below.

\n

\n \"Signup\"\n

\n

You will get an email with a .p12 file attached, which is your WebID certificate. The certificate's password is the one you entered in the signup form.

\n
\n
\n
\n

You'll need a PEM version of the certificate for use with the command line interface scripts. During setup, it is stored under\n ssl/owner/cert.pem. If you got the certificate by email, you need to convert the PKCS12 file to PEM using OpenSSL.

\n
\n

Unlike most LinkedDataHub resources, your WebID profile will have public access as required by the protocol. Your email address will be hidden however.

\n
\n
\n
\n

Install certificate

\n

The final step is to install the client certificate into your web browser. It is done by importing the .p12\n file using the browser's certificate manager and providing the password that you supplied during signup. The\n manager dialog can be opened following the steps below, depending on which browser you use:

\n
\n
Google Chrome
\n
Settings > Advanced > Manage Certificates > Import...
\n
Mozilla Firefox
\n
Options > Privacy & Security > View Certificates... > Import...
\n
Apple Safari
\n
The file is installed directly into the operating system. Open the file and import it using the\n Keychain Access\n tool. Drag the .p12 file to the login section.
\n
Microsoft Edge
\n
Does not support certificate management, you need to install the file into Windows.\n Read more here.
\n
\n

You need to install the certificate on all devices/browsers that you are using to access LinkedDataHub.

\n
\n
\n

Log in

\n

Open the URL of the LinkedDataHub instance in the web browser (that you installed the WebID certificate into). Using a local setup, it runs on https://localhost:4443/ by default.

\n

With the certificate installed, there is no login procedure — you are automatically authenticated on all\n LinkedDataHub applications. This is known as Single sign-on (SSO).

\n

Applications can provide public access to some or all documents, meaning you can freely browse their public resources\n and perform actions that are allowed for public access. In order to access protected (non-public) resources, as well\n as to access administration application, users have to be authenticated as well authorized (authorizations\n can be requested).

\n
\n

Authenticated agents are not guaranteed to have access to all resources. Different access levels for\n different agents can be specified by the application administrators.

\n
\n
\n
\n
\n

Click the Login with Google button in the navbar to authenticate with your Google account.

\n

If the email address of your Google account matches the dataspace owner's email address that was specified during setup, you will be authenticated as the owner with full control access rights.

\n
\n

Login with Google is only enabled if LinkedDataHub was configured with social login.

\n
\n
\n
\n
\n
\n

Are you in? Then continue the get started guide or take a look at the UI overview.

\n
"^^ .