|
7 | 7 | dct:title "Get an account" ; |
8 | 8 | dct:description "How to get login to LinkedDataHub" ; |
9 | 9 | rdf:_1 <#content> . |
10 | | - |
| 10 | + |
11 | 11 | <#content> a ldh:XHTML ; |
12 | 12 | rdf:value """<div xmlns="http://www.w3.org/1999/xhtml"> |
13 | 13 | <p class="lead">This guide describes how to login to LinkedDataHub.</p> |
14 | 14 | <div> |
| 15 | + <div class="alert alert-info"> |
| 16 | + <p>In order to authenticate as the <em>owner</em> of a LinkedDataHub instance, you need to use the WebID authentication method.</p> |
| 17 | + </div> |
15 | 18 | <div class="tabbable"> |
16 | 19 | <ul class="nav nav-tabs"> |
17 | | - <li class="active"><a>LinkedDataHub</a></li> |
18 | | - <li><a>LinkedDataHub Cloud</a></li> |
| 20 | + <li class="active"><a>Get WebID</a></li> |
| 21 | + <li><a>Login with Google</a></li> |
19 | 22 | </ul> |
20 | 23 | <div class="tab-content"> |
21 | 24 | <div class="tab-pane active"> |
22 | | - <div class="alert alert-info"> |
23 | | - <p>In order to authenticate as the <em>owner</em> of a LinkedDataHub instance, you need to use the WebID authentication method.</p> |
24 | | - </div> |
25 | | - <div class="tabbable"> |
26 | | - <ul class="nav nav-tabs"> |
27 | | - <li class="active"><a>Get WebID</a></li> |
28 | | - <li><a>Login with Google</a></li> |
29 | | - </ul> |
30 | | - <div class="tab-content"> |
31 | | - <div class="tab-pane active"> |
32 | | - <div> |
33 | | - <h2 id="get-cert">Get certificate</h2> |
34 | | - <p>LinkedDataHub uses WebID as the <a href="https://en.wikipedia.org/wiki/Single_sign-on" target="_blank">Single sign-on</a> (SSO) |
35 | | - 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. |
36 | | - <a href="http://webid.info" target="_blank">Read more about WebID</a>.</p> |
37 | | - <p>There are two ways to get a LinkedDataHub WebID: setup and signup.</p> |
38 | | - <div class="tabbable"> |
39 | | - <ul class="nav nav-tabs"> |
40 | | - <li class="active"><a>Setup</a></li> |
41 | | - <li><a>Signup</a></li> |
42 | | - </ul> |
43 | | - <div class="tab-content"> |
44 | | - <div class="tab-pane active"> |
45 | | - <p>Complete the <a href="../setup/">setup</a> and run own an instance of LinkedDataHub.</p> |
46 | | - <p>The <samp>ssl/owner/keystore.p12</samp> file is your WebID certificate. The password is the <samp>owner_cert_password</samp> Docker secret value.</p> |
47 | | - </div> |
48 | | - <div class="tab-pane"> |
49 | | - <p>Sign up to an existing instance of LinkedDataHub. Click the <span class="btn btn-primary">Sign up</span> button and fill out the form with your |
50 | | - details to get a WebID, as shown below.</p> |
51 | | - <p> |
52 | | - <img alt="Signup" src="../../uploads/cf383c52ac014823a2627b055cca06b21d8fe8b0"></img> |
53 | | - </p> |
54 | | - <p>You will get an email with a <samp>.p12</samp> file attached, which is your WebID certificate. The certificate's password is the one you entered in the signup form.</p> |
55 | | - </div> |
56 | | - </div> |
57 | | - </div> |
58 | | - <p>You'll need a PEM version of the certificate for use with the <a href="../../reference/command-line-interface/">command line interface</a> scripts. During setup, it is stored under |
59 | | - <samp>ssl/owner/cert.pem</samp>. If you got the certificate by email, you need to <a href="https://stackoverflow.com/a/15144560/1003113" target="_blank">convert the PKCS12 file to PEM using OpenSSL</a>.</p> |
60 | | - <div class="alert alert-info"> |
61 | | - <p>Unlike most LinkedDataHub resources, your WebID profile will have <em>public access</em> as required by the protocol. Your email address will be hidden however.</p> |
62 | | - </div> |
63 | | - </div> |
64 | | - <div> |
65 | | - <h2 id="install-cert">Install certificate</h2> |
66 | | - <p>The final step is to install the client certificate into your web browser. It is done by importing the <samp>.p12</samp> |
67 | | - file using the browser's certificate manager and providing the password that you supplied during signup. The |
68 | | - manager dialog can be opened following the steps below, depending on which browser you use:</p> |
69 | | - <dl> |
70 | | - <dt>Google Chrome</dt> |
71 | | - <dd><samp>Settings > Advanced > Manage Certificates > Import...</samp></dd> |
72 | | - <dt>Mozilla Firefox</dt> |
73 | | - <dd><samp>Options > Privacy & Security > View Certificates... > Import...</samp></dd> |
74 | | - <dt>Apple Safari</dt> |
75 | | - <dd>The file is installed directly into the operating system. Open the file and import it using the |
76 | | - <a href="https://support.apple.com/guide/keychain-access/what-is-keychain-access-kyca1083/mac" target="_blank">Keychain Access</a> |
77 | | - tool. Drag the <samp>.p12</samp> file to the <samp>login</samp> section.</dd> |
78 | | - <dt>Microsoft Edge</dt> |
79 | | - <dd>Does not support certificate management, you need to install the file into Windows. |
80 | | - <a href="https://social.technet.microsoft.com/Forums/en-US/18301fff-0467-4e41-8dee-4e44823ed5bf/microsoft-edge-browser-and-ssl-certificates?forum=win10itprogeneral" target="_blank">Read more here</a>.</dd> |
81 | | - </dl> |
82 | | - <p>You need to install the certificate on all devices/browsers that you are using to access LinkedDataHub.</p> |
| 25 | + <div> |
| 26 | + <h2 id="get-cert">Get certificate</h2> |
| 27 | + <p>LinkedDataHub uses WebID as the <a href="https://en.wikipedia.org/wiki/Single_sign-on" target="_blank">Single sign-on</a> (SSO) |
| 28 | + 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. |
| 29 | + <a href="http://webid.info" target="_blank">Read more about WebID</a>.</p> |
| 30 | + <p>There are two ways to get a LinkedDataHub WebID: setup and signup.</p> |
| 31 | + <div class="tabbable"> |
| 32 | + <ul class="nav nav-tabs"> |
| 33 | + <li class="active"><a>Setup</a></li> |
| 34 | + <li><a>Signup</a></li> |
| 35 | + </ul> |
| 36 | + <div class="tab-content"> |
| 37 | + <div class="tab-pane active"> |
| 38 | + <p>Complete the <a href="../setup/">setup</a> and run own an instance of LinkedDataHub.</p> |
| 39 | + <p>The <samp>ssl/owner/keystore.p12</samp> file is your WebID certificate. The password is the <samp>owner_cert_password</samp> Docker secret value.</p> |
83 | 40 | </div> |
84 | | - <div> |
85 | | - <h2 id="log-in">Log in</h2> |
86 | | - <p>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 <a href="https://localhost:4443/" target="_blank">https://localhost:4443/</a> by default. </p> |
87 | | - <p>With the certificate installed, there is no login procedure — you are automatically <em>authenticated</em> on all |
88 | | - LinkedDataHub applications. This is known as Single sign-on (SSO).</p> |
89 | | - <p>Applications can provide public access to some or all documents, meaning you can freely browse their public resources |
90 | | - and perform actions that are allowed for public access. In order to access protected (non-public) resources, as well |
91 | | - as to access administration application, users have to be authenticated as well <em>authorized</em> (authorizations |
92 | | - can be <a href="../../reference/administration/acl/#auth-requests">requested</a>).</p> |
93 | | - <div class="alert alert-info"> |
94 | | - <p>Authenticated agents <em>are not guaranteed to have access</em> to all resources. Different access levels for |
95 | | - different agents can be specified by the application administrators.</p> |
96 | | - </div> |
| 41 | + <div class="tab-pane"> |
| 42 | + <p>Sign up to an existing instance of LinkedDataHub. Click the <span class="btn btn-primary">Sign up</span> button and fill out the form with your |
| 43 | + details to get a WebID, as shown below.</p> |
| 44 | + <p> |
| 45 | + <img alt="Signup" src="../../uploads/cf383c52ac014823a2627b055cca06b21d8fe8b0"></img> |
| 46 | + </p> |
| 47 | + <p>You will get an email with a <samp>.p12</samp> file attached, which is your WebID certificate. The certificate's password is the one you entered in the signup form.</p> |
97 | 48 | </div> |
98 | | - </div> |
99 | | - <div class="tab-pane"> |
100 | | - <p>Click the <span class="btn btn-primary">Login with Google</span> button in the navbar to authenticate with your Google account.</p> |
101 | | - <p>If the email address of your Google account matches the dataspace owner's email address that was specified during <a href="../setup/">setup</a>, you will be authenticated as the owner with <a href="../../reference/administration/acl/">full control</a> access rights.</p> |
102 | | - <div class="alert alert-info"> |
103 | | - <p>Login with Google is only enabled if LinkedDataHub was <a href="../../reference/configuration/#social-login">configured with social login</a>.</p> |
104 | | - </div> |
105 | | - </div> |
106 | | - </div> |
| 49 | + </div> |
| 50 | + </div> |
| 51 | + <p>You'll need a PEM version of the certificate for use with the <a href="../../reference/command-line-interface/">command line interface</a> scripts. During setup, it is stored under |
| 52 | + <samp>ssl/owner/cert.pem</samp>. If you got the certificate by email, you need to <a href="https://stackoverflow.com/a/15144560/1003113" target="_blank">convert the PKCS12 file to PEM using OpenSSL</a>.</p> |
| 53 | + <div class="alert alert-info"> |
| 54 | + <p>Unlike most LinkedDataHub resources, your WebID profile will have <em>public access</em> as required by the protocol. Your email address will be hidden however.</p> |
| 55 | + </div> |
| 56 | + </div> |
| 57 | + <div> |
| 58 | + <h2 id="install-cert">Install certificate</h2> |
| 59 | + <p>The final step is to install the client certificate into your web browser. It is done by importing the <samp>.p12</samp> |
| 60 | + file using the browser's certificate manager and providing the password that you supplied during signup. The |
| 61 | + manager dialog can be opened following the steps below, depending on which browser you use:</p> |
| 62 | + <dl> |
| 63 | + <dt>Google Chrome</dt> |
| 64 | + <dd><samp>Settings > Advanced > Manage Certificates > Import...</samp></dd> |
| 65 | + <dt>Mozilla Firefox</dt> |
| 66 | + <dd><samp>Options > Privacy & Security > View Certificates... > Import...</samp></dd> |
| 67 | + <dt>Apple Safari</dt> |
| 68 | + <dd>The file is installed directly into the operating system. Open the file and import it using the |
| 69 | + <a href="https://support.apple.com/guide/keychain-access/what-is-keychain-access-kyca1083/mac" target="_blank">Keychain Access</a> |
| 70 | + tool. Drag the <samp>.p12</samp> file to the <samp>login</samp> section.</dd> |
| 71 | + <dt>Microsoft Edge</dt> |
| 72 | + <dd>Does not support certificate management, you need to install the file into Windows. |
| 73 | + <a href="https://social.technet.microsoft.com/Forums/en-US/18301fff-0467-4e41-8dee-4e44823ed5bf/microsoft-edge-browser-and-ssl-certificates?forum=win10itprogeneral" target="_blank">Read more here</a>.</dd> |
| 74 | + </dl> |
| 75 | + <p>You need to install the certificate on all devices/browsers that you are using to access LinkedDataHub.</p> |
| 76 | + </div> |
| 77 | + <div> |
| 78 | + <h2 id="log-in">Log in</h2> |
| 79 | + <p>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 <a href="https://localhost:4443/" target="_blank">https://localhost:4443/</a> by default. </p> |
| 80 | + <p>With the certificate installed, there is no login procedure — you are automatically <em>authenticated</em> on all |
| 81 | + LinkedDataHub applications. This is known as Single sign-on (SSO).</p> |
| 82 | + <p>Applications can provide public access to some or all documents, meaning you can freely browse their public resources |
| 83 | + and perform actions that are allowed for public access. In order to access protected (non-public) resources, as well |
| 84 | + as to access administration application, users have to be authenticated as well <em>authorized</em> (authorizations |
| 85 | + can be <a href="../../reference/administration/acl/#auth-requests">requested</a>).</p> |
| 86 | + <div class="alert alert-info"> |
| 87 | + <p>Authenticated agents <em>are not guaranteed to have access</em> to all resources. Different access levels for |
| 88 | + different agents can be specified by the application administrators.</p> |
| 89 | + </div> |
| 90 | + </div> |
| 91 | + </div> |
| 92 | + <div class="tab-pane"> |
| 93 | + <p>Click the <span class="btn btn-primary">Login with Google</span> button in the navbar to authenticate with your Google account.</p> |
| 94 | + <p>If the email address of your Google account matches the dataspace owner's email address that was specified during <a href="../setup/">setup</a>, you will be authenticated as the owner with <a href="../../reference/administration/acl/">full control</a> access rights.</p> |
| 95 | + <div class="alert alert-info"> |
| 96 | + <p>Login with Google is only enabled if LinkedDataHub was <a href="../../reference/configuration/#social-login">configured with social login</a>.</p> |
107 | 97 | </div> |
108 | | - </div> |
109 | | - <div class="tab-pane"> |
110 | | - <p>To sign in, click on the <span class="btn btn-primary">Login with Google</span> button. A unique agent URI will be assigned to you and used to authenticate you with the applications on the platform.</p> |
111 | | - </div> |
| 98 | + </div> |
112 | 99 | </div> |
113 | 100 | </div> |
114 | 101 | </div> |
|
0 commit comments