Skip to content
Snippets Groups Projects
Commit 2ea96130 authored by Larbi Gharib's avatar Larbi Gharib
Browse files

Images markdown path 

Change-Id: I5c3d64f4c3cea5d356dd4d6eb2fdaeb01c5d24d6
parent 39ec1e02
No related branches found
No related tags found
No related merge requests found
Expand all Hide whitespace changes
Inline Side-by-side
Showing
with 126 additions and 128 deletions
userguide/docs/admin.md
+ 10
− 4
View file @ 2ea96130
<style type='text/css'>
img{
height:400px;
}
</style>
# Admin Guide
By default JAMS runs an embedded tomcat server visible on port 8080, however this is not practical for many reasons. This guide is designed to help you setup Jams to run in a production environment.
......@@ -10,9 +16,10 @@ recommend users to place it behind Nginx or a similar web server which proxies r
The following is an example map of how you could configure JAMS behind Nginx (the process would be similar if you wanted to use any other type of proxying solution):
<p align="center">
<img src="../img/map.png" alt="Create an admin account" style="height:400px;"/>
</p>
![alt text][map]
[map]: https://static.savoirfairelinux.com/img/jams/map.png "Create an admin account"
The IP 10.10.0.1 is random, and should be seen as an example.
......@@ -259,5 +266,4 @@ ExecStart=/usr/bin/java -jar [DIRECTORY WHERE JAMS WAS UNZIPPED]/jams-launcher.j
[Install]
WantedBy=multi-user.target
</b>
The parameters PORT, SSL_CERTIFICATE and SSL_CERTIFICATE_KEY are optional (however, PORT can be used alone whereas the SSL_CERTIFICATE comes in pair with SSL_CERTIFICATE_KEY)
\ No newline at end of file
userguide/docs/clients.md
+ 41
− 33
View file @ 2ea96130
<style type='text/css'>
img{
height:400px;
}
</style>
# Client Guide
Depending on your operating system, we have included the tutorial on how to connect to the management server from the Windows, MacOS, Android and iOS clients.
......@@ -14,15 +20,15 @@ For the purposes of this tutorial, we assume that
Open Jami, go to the login page. Click on "Advanced":
<p align="center">
<img src="../img/client/linux/linux-step1.png" alt="Step 1" style="height:400px;"/>
</p>
![alt text][linuxstep1]
[linuxstep1]: https://static.savoirfairelinux.com/img/jams/client/linux/linux-step1.png "Step1"
Select the option **"Connect to a JAMS server"** which will lead you to the following screen:
<p align="center">
<img src="../img/client/linux/linux-step2.png" alt="Step 2" style="height:400px;"/>
</p>
![alt text][linuxstep2]
[linuxstep2]: https://static.savoirfairelinux.com/img/jams/client/linux/linux-step2.png "Step2"
The **Jami Account Management Server URL** in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.
......@@ -30,15 +36,15 @@ The **Jami Account Management Server URL** in this case would be the DNS address
Open Jami, go to the login page. Click on "Advanced":
<p align="center">
<img src="../img/client/windows/windows-step1.png" alt="Step 1" style="height:400px;"/>
</p>
![alt text][windowsstep1]
[windowsstep1]: https://static.savoirfairelinux.com/img/jams/client/windows/windows-step1.png "Windows step 1"
Select the option **"Connect to a JAMS server"** which will lead you to the following screen:
<p align="center">
<img src="../img/client/windows/windows-step2.png" alt="Step 2" style="height:400px;"/>
</p>
![alt text][windowsstep2]
[windowsstep2]: https://static.savoirfairelinux.com/img/jams/client/windows/windows-step2.png "Windows step 2"
The **Jami Account Management Server URL** in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.
......@@ -46,15 +52,16 @@ The **Jami Account Management Server URL** in this case would be the DNS address
Open Jami, go to the login page. Click on "Advanced":
<p align="center">
<img src="../img/client/macos/macos-step1.png" alt="Step 1" style="height:400px;"/>
</p>
![alt text][macosstep1]
[macosstep1]: https://static.savoirfairelinux.com/img/jams/client/macos/macos-step1.png "MacOS step 1"
Select the option **"Connect to account manager"** which will lead you to the following screen:
<p align="center">
<img src="../img/client/macos/macos-step2.png" alt="Step 2" style="height:400px;"/>
</p>
![alt text][macosstep2]
[macosstep2]: https://static.savoirfairelinux.com/img/jams/client/macos/macos-step2.png "MacOS step 2"
The **Jami Account Management Server URL** in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.
......@@ -62,28 +69,29 @@ The **Jami Account Management Server URL** in this case would be the DNS address
Open Jami, go to the login page.
<p align="center">
<img src="../img/client/android/android-step1.png" alt="Step 1" style="height:400px;"/>
</p>
![alt text][androidstep1]
[androidstep1]: https://static.savoirfairelinux.com/img/jams/client/android/android-step1.png "Android step 1"
Select the option **"Connect to management server"** which will lead you to the following screen:
<p align="center">
<img src="../img/client/android/android-step2.png" alt="Step 2" style="height:400px;"/>
</p>
![alt text][androidstep2]
[androidstep2]: https://static.savoirfairelinux.com/img/jams/client/android/android-step2.png "Android step 2"
The server in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.
## Connect from an iOS device
Open Jami, go to the login page.
<p align="center">
<img src="../img/client/ios/ios-step1.png" alt="Step 1" style="height:400px;"/>
</p>
![alt text][iosstep1]
[iosstep1]: https://static.savoirfairelinux.com/img/jams/client/ios/ios-step1.png "iOS step 1"
Select the option **"Connect to account manager"** which will lead you to the following screen:
<p align="center">
<img src="../img/client/ios/ios-step2.png" alt="Step 2" style="height:400px;"/>
</p>
![alt text][iosstep2]
[iosstep2]: https://static.savoirfairelinux.com/img/jams/client/ios/ios-step2.png "iOS step 2"
The server in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.
\ No newline at end of file
userguide/docs/img/device_enroll.png
+ 0
− 0
View replaced file @ 39ec1e02 View file @ 2ea96130
userguide/docs/img/device_enroll.png

9.93 KiB | W: | H:

userguide/docs/img/device_enroll.png

13.6 KiB | W: | H:

userguide/docs/img/device_enroll.png
userguide/docs/img/device_enroll.png
userguide/docs/img/device_enroll.png
userguide/docs/img/device_enroll.png
  • 2-up
  • Swipe
  • Onion skin
userguide/docs/index.md
+ 33
− 26
View file @ 2ea96130
<style type='text/css'>
img{
height:400px;
}
</style>
# Getting Started
JAMS is a server application used to enroll Jami clients into an Enterprise context. Currently, JAMS supports 3 sources for user authentication: LDAP, Active Directory and an embedded database.
......@@ -25,9 +31,9 @@ In order to be completely secure, JAMS does not generate certificates for device
The diagram below shows the entire process of how a device enrolls with JAMS:
<p align="center">
<img src="img/device_enroll.png" alt="Device Enrollement" style="height:400px;" />
</p>
![alt text][deviceenrollement]
[deviceenrollement]: https://static.savoirfairelinux.com/img/jams/device_enroll.png "Device Enrollement"
​
## Getting Started
......@@ -63,10 +69,9 @@ Please note that any port above 1024 can be safely used to run JAMS.
This account will have administrative control and the rights to manage your users and group of Jami users.
<p align="center">
<img src="img/step1.png" alt="Create an admin account" style="height:400px;"/>
</p>
![alt text][step1]
[step1]: https://static.savoirfairelinux.com/img/jams/step1.png "Create an admin account"
## Step 2: setup the Certification Authority
......@@ -74,10 +79,13 @@ The second step is to define your Certification Authority.
**Important:** a CA is not a server-side ssl certificate, it is a certificate which has the power to issue other certificates. Do not use the import option unless your company's security officer has issued you a CA certificate. Most commercially available certificates (i.e. those issued by godaddy, letsencrypt, etc... ) are not CA certificates. If you are an end-user we highly recommend you use to create a self-signed CA option as providing an incorrect certificate type will lead to a non-functional server.
<p align="center">
<img src="img/step2-1.png" alt="Create an admin account" style="height:400px;"/>
<img src="img/step2-2.png" alt="Create an admin account" style="height:400px;"/>
</p>
![alt text][step1-1]
[step1-1]: https://static.savoirfairelinux.com/img/jams/step2-1.png "Certification Authority Create"
![alt text][step1-2]
[step1-2]: https://static.savoirfairelinux.com/img/jams/step2-2.png "Certification Authority Import"
This certificate will be used to sign the enrollement requests which come from Jami devices. If you are not familiar with the X509 standard, we highly recommend you read the following
......@@ -100,9 +108,9 @@ JAMS supports 3 different sources for the authentication of users:
If your company provides you with LDAP directory for user management, you will need to know its access information and a automated account which has read-only rights to do use look-ups.
<p align="center">
<img src="img/ldap.png" style="height:400px;"/>
</p>
![alt text][ldap]
[ldap]: https://static.savoirfairelinux.com/img/jams/ldap.png "LDAP"
Your admin should provide you most of this information but we do provide a detailed overview over each field in case you need some extra help:
......@@ -122,10 +130,9 @@ Your admin should provide you most of this information but we do provide a detai
If your company provides you with Active Directory for user management, you will need to know its access information and an automated account which has read-only rights to do use look-ups.
![alt text][ad]
<p align="center">
<img src="img/ad.png" style="height:400px;"/>
</p>
[ad]: https://static.savoirfairelinux.com/img/jams/ad.png "AD"
Your admin should provide you most of this information but we do provide a detailed overview over each field in case you need some extra help:
......@@ -144,9 +151,9 @@ Your admin should provide you most of this information but we do provide a detai
The local database does not require any additional configuration, everything in the process is automated. This option allows you to create Jami users on the fly directly from the JAMS interface.
<p align="center">
<img src="img/local.png" style="height:400px;"/>
</p>
![alt text][local]
[local]: https://static.savoirfairelinux.com/img/jams/local.png "Local"
**Advanced settings:** by default, the option "Use public nameserver" is disabled. Usernames of your Jami users will not be stored on the public Jami nameserver and your users will only be able to communicate with users from your organization.
......@@ -154,9 +161,9 @@ If you want your users to be searchable by external users and allow them to comm
## Step 4: setup the server parameters
<p align="center">
<img src="img/step4.png" style="height:400px;"/>
</p>
![alt text][step4]
[step4]: https://static.savoirfairelinux.com/img/jams/step4.png "Setup server parameters"
| Parameter | Details |
| ------------- |------------- |
......@@ -173,8 +180,8 @@ If you want your users to be searchable by external users and allow them to comm
Click on "Set Server Parameters" to finalize the configuration.
You will be redirected to the JAMS interface.
<p align="center">
<img src="img/jams-dashboard.png" style="height:400px;"/>
</p>
![alt text][jamsdashboard]
[jamsdashboard]: https://static.savoirfairelinux.com/img/jams/jams-dashboard.png "Jams dashboard"
If you have configured JAMS with your LDAP or Active Directory, the list of users should of your organization shoud be visible in JAMS. If you have selected the local embedded database, you can now start creating new users by clicking on "Create User"
If you have configured JAMS with your LDAP or Active Directory, the list of users should of your organization shoud be visible in JAMS. If you have selected the local embedded database, you can now start creating new users by clicking on "Create User"
\ No newline at end of file
userguide/site/admin/index.html
+ 7
− 4
View file @ 2ea96130
......@@ -92,15 +92,18 @@
</div>
</div></div>
<div class="col-md-9" role="main"><a class="md-content__icon pdf-download-btn" download href="../pdf/combined.pdf" title="Download"><i class="fa fas fa-download"></i><small> PDF</small></a>
<style type="text/css">
img{
height:400px;
}
</style>
<h1 id="admin-guide">Admin Guide</h1>
<p>By default JAMS runs an embedded tomcat server visible on port 8080, however this is not practical for many reasons. This guide is designed to help you setup Jams to run in a production environment.</p>
<h2 id="jams-nginx">JAMS &amp; Nginx</h2>
<p>It is generally not recommended to expose JAMS directly to the outside world and while it is required to run JAMS in SSL mode, we usually
recommend users to place it behind Nginx or a similar web server which proxies requests between the outside world and Jams.</p>
<p>The following is an example map of how you could configure JAMS behind Nginx (the process would be similar if you wanted to use any other type of proxying solution):</p>
<p align="center">
<img alt="Create an admin account" src="../img/map.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/map.png" title="Create an admin account"/></p>
<p>The IP 10.10.0.1 is random, and should be seen as an example.</p>
<p>Typically you would add a new site called <code>jams-site.conf</code> to your nginx configurations which would contain the following entries if you wanted to place an SSL certificate at the Nginx level: <pre>
<b>server {
......@@ -288,7 +291,7 @@ ExecStart=/usr/bin/java -jar [DIRECTORY WHERE JAMS WAS UNZIPPED]/jams-launcher.j
<p>[Install]
WantedBy=multi-user.target
</p></div></div></div></body></html>
<p>The parameters PORT, SSL_CERTIFICATE and SSL_CERTIFICATE_KEY are optional (however, PORT can be used alone whereas the SSL_CERTIFICATE comes in pair with SSL_CERTIFICATE_KEY)</p>
The parameters PORT, SSL_CERTIFICATE and SSL_CERTIFICATE_KEY are optional (however, PORT can be used alone whereas the SSL_CERTIFICATE comes in pair with SSL_CERTIFICATE_KEY)
<footer class="col-md-12">
......
userguide/site/clients/index.html
+ 16
− 31
View file @ 2ea96130
......@@ -96,6 +96,11 @@
</div>
</div></div>
<div class="col-md-9" role="main"><a class="md-content__icon pdf-download-btn" download href="../pdf/combined.pdf" title="Download"><i class="fa fas fa-download"></i><small> PDF</small></a>
<style type="text/css">
img{
height:400px;
}
</style>
<h1 id="client-guide">Client Guide</h1>
<p>Depending on your operating system, we have included the tutorial on how to connect to the management server from the Windows, MacOS, Android and iOS clients.</p>
<p>For the purposes of this tutorial, we assume that</p>
......@@ -109,53 +114,33 @@
</ol>
<h2 id="connect-from-a-linux-device">Connect from a Linux device</h2>
<p>Open Jami, go to the login page. Click on "Advanced":</p>
<p align="center">
<img alt="Step 1" src="../img/client/linux/linux-step1.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/linux/linux-step1.png" title="Step1"/></p>
<p>Select the option <strong>"Connect to a JAMS server"</strong> which will lead you to the following screen:</p>
<p align="center">
<img alt="Step 2" src="../img/client/linux/linux-step2.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/linux/linux-step2.png" title="Step2"/></p>
<p>The <strong>Jami Account Management Server URL</strong> in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.</p>
<h2 id="connect-from-a-windows-device">Connect from a Windows device</h2>
<p>Open Jami, go to the login page. Click on "Advanced":</p>
<p align="center">
<img alt="Step 1" src="../img/client/windows/windows-step1.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/windows/windows-step1.png" title="Windows step 1"/></p>
<p>Select the option <strong>"Connect to a JAMS server"</strong> which will lead you to the following screen:</p>
<p align="center">
<img alt="Step 2" src="../img/client/windows/windows-step2.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/windows/windows-step2.png" title="Windows step 2"/></p>
<p>The <strong>Jami Account Management Server URL</strong> in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.</p>
<h2 id="connect-from-a-macos-device">Connect from a MacOS device</h2>
<p>Open Jami, go to the login page. Click on "Advanced":</p>
<p align="center">
<img alt="Step 1" src="../img/client/macos/macos-step1.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/macos/macos-step1.png" title="MacOS step 1"/></p>
<p>Select the option <strong>"Connect to account manager"</strong> which will lead you to the following screen:</p>
<p align="center">
<img alt="Step 2" src="../img/client/macos/macos-step2.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/macos/macos-step2.png" title="MacOS step 2"/></p>
<p>The <strong>Jami Account Management Server URL</strong> in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.</p>
<h2 id="connect-from-an-android-device">Connect from an Android device</h2>
<p>Open Jami, go to the login page.</p>
<p align="center">
<img alt="Step 1" src="../img/client/android/android-step1.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/android/android-step1.png" title="Android step 1"/></p>
<p>Select the option <strong>"Connect to management server"</strong> which will lead you to the following screen:</p>
<p align="center">
<img alt="Step 2" src="../img/client/android/android-step2.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/android/android-step2.png" title="Android step 2"/></p>
<p>The server in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.</p>
<h2 id="connect-from-an-ios-device">Connect from an iOS device</h2>
<p>Open Jami, go to the login page.
<p align="center">
<img alt="Step 1" src="../img/client/ios/ios-step1.png" style="height:400px;"/>
</p></p>
<p>Open Jami, go to the login page.</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/ios/ios-step1.png" title="iOS step 1"/></p>
<p>Select the option <strong>"Connect to account manager"</strong> which will lead you to the following screen:</p>
<p align="center">
<img alt="Step 2" src="../img/client/ios/ios-step2.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/client/ios/ios-step2.png" title="iOS step 2"/></p>
<p>The server in this case would be the DNS address of your server and the username and password which correspond to your account. If you have configured the server with an LDAP/AD backend, it would be your LDAP/AD username and password.</p></div>
</div>
</div>
......
userguide/site/img/device_enroll.png
+ 0
− 0
View replaced file @ 39ec1e02 View file @ 2ea96130
userguide/site/img/device_enroll.png

9.93 KiB | W: | H:

userguide/site/img/device_enroll.png

13.6 KiB | W: | H:

userguide/site/img/device_enroll.png
userguide/site/img/device_enroll.png
userguide/site/img/device_enroll.png
userguide/site/img/device_enroll.png
  • 2-up
  • Swipe
  • Onion skin
userguide/site/index.html
+ 15
− 26
View file @ 2ea96130
......@@ -109,6 +109,11 @@
</div>
</div></div>
<div class="col-md-9" role="main"><a class="md-content__icon pdf-download-btn" download href="pdf/combined.pdf" title="Download"><i class="fa fas fa-download"></i><small> PDF</small></a>
<style type="text/css">
img{
height:400px;
}
</style>
<h1 id="getting-started">Getting Started</h1>
<p>JAMS is a server application used to enroll Jami clients into an Enterprise context. Currently, JAMS supports 3 sources for user authentication: LDAP, Active Directory and an embedded database.</p>
<h2 id="obtaining-jams">Obtaining JAMS</h2>
......@@ -126,9 +131,7 @@
<p>In the JAMS paradigm, a device (Jami client) requests a certificate to the server then presents it to other devices to be recognized as a valid member of the organization. Therefore, JAMS must be provided with a certificate authority in order to work properly.</p>
<p>In order to be completely secure, JAMS does not generate certificates for devices, but instead issues certificates based on a certificate signing request sent to it by the device, therefore removing the need to send a private key over the wire.</p>
<p>The diagram below shows the entire process of how a device enrolls with JAMS:</p>
<p align="center">
<img alt="Device Enrollement" src="img/device_enroll.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/device_enroll.png" title="Device Enrollement"/></p>
<p>​ </p>
<h2 id="getting-started_1">Getting Started</h2>
<ol>
......@@ -176,16 +179,12 @@ An example of the command would be: </p>
<p>Please note that any port above 1024 can be safely used to run JAMS.</p>
<h2 id="step-1-create-your-admininistrator-account">Step 1: create your admininistrator account</h2>
<p>This account will have administrative control and the rights to manage your users and group of Jami users.</p>
<p align="center">
<img alt="Create an admin account" src="img/step1.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/step1.png" title="Create an admin account"/></p>
<h2 id="step-2-setup-the-certification-authority">Step 2: setup the Certification Authority</h2>
<p>The second step is to define your Certification Authority. </p>
<p><strong>Important:</strong> a CA is not a server-side ssl certificate, it is a certificate which has the power to issue other certificates. Do not use the import option unless your company's security officer has issued you a CA certificate. Most commercially available certificates (i.e. those issued by godaddy, letsencrypt, etc... ) are not CA certificates. If you are an end-user we highly recommend you use to create a self-signed CA option as providing an incorrect certificate type will lead to a non-functional server.</p>
<p align="center">
<img alt="Create an admin account" src="img/step2-1.png" style="height:400px;"/>
<img alt="Create an admin account" src="img/step2-2.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/step2-1.png" title="Certification Authority Create"/></p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/step2-2.png" title="Certification Authority Import"/></p>
<p>This certificate will be used to sign the enrollement requests which come from Jami devices. If you are not familiar with the X509 standard, we highly recommend you read the following
articles to get familiar with the processes and practices which surround it:</p>
<p><a href="https://www.securew2.com/blog/public-key-infrastructure-explained/">https://www.securew2.com/blog/public-key-infrastructure-explained/</a>
......@@ -200,9 +199,7 @@ articles to get familiar with the processes and practices which surround it:</p>
<p><br/></p>
<h3 id="option-1-ldap-authentication">Option 1: LDAP authentication</h3>
<p>If your company provides you with LDAP directory for user management, you will need to know its access information and a automated account which has read-only rights to do use look-ups.</p>
<p align="center">
<img src="img/ldap.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/ldap.png" title="LDAP"/></p>
<p>Your admin should provide you most of this information but we do provide a detailed overview over each field in case you need some extra help:</p>
<table>
<thead>
......@@ -241,9 +238,7 @@ articles to get familiar with the processes and practices which surround it:</p>
<p><br/></p>
<h3 id="option-2-microsoft-active-directory">Option 2: Microsoft Active Directory</h3>
<p>If your company provides you with Active Directory for user management, you will need to know its access information and an automated account which has read-only rights to do use look-ups.</p>
<p align="center">
<img src="img/ad.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/ad.png" title="AD"/></p>
<p>Your admin should provide you most of this information but we do provide a detailed overview over each field in case you need some extra help:</p>
<table>
<thead>
......@@ -282,15 +277,11 @@ articles to get familiar with the processes and practices which surround it:</p>
<p><br/></p>
<h3 id="option-3-local-embedded-database">Option 3: local embedded database</h3>
<p>The local database does not require any additional configuration, everything in the process is automated. This option allows you to create Jami users on the fly directly from the JAMS interface.</p>
<p align="center">
<img src="img/local.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/local.png" title="Local"/></p>
<p><strong>Advanced settings:</strong> by default, the option "Use public nameserver" is disabled. Usernames of your Jami users will not be stored on the public Jami nameserver and your users will only be able to communicate with users from your organization.</p>
<p>If you want your users to be searchable by external users and allow them to communicate with any Jami users, and not only the one from your organization, enable this option,</p>
<h2 id="step-4-setup-the-server-parameters">Step 4: setup the server parameters</h2>
<p align="center">
<img src="img/step4.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/step4.png" title="Setup server parameters"/></p>
<table>
<thead>
<tr>
......@@ -321,9 +312,7 @@ articles to get familiar with the processes and practices which surround it:</p>
<p><br/></p>
<p>Click on "Set Server Parameters" to finalize the configuration.
You will be redirected to the JAMS interface.</p>
<p align="center">
<img src="img/jams-dashboard.png" style="height:400px;"/>
</p>
<p><img alt="alt text" src="https://static.savoirfairelinux.com/img/jams/jams-dashboard.png" title="Jams dashboard"/></p>
<p>If you have configured JAMS with your LDAP or Active Directory, the list of users should of your organization shoud be visible in JAMS. If you have selected the local embedded database, you can now start creating new users by clicking on "Create User"</p></div>
</div>
</div>
......@@ -404,5 +393,5 @@ You will be redirected to the JAMS interface.</p>
</html>
<!--
MkDocs version : 1.1.2
Build Date UTC : 2020-11-22 01:43:55.216806+00:00
Build Date UTC : 2020-12-11 17:41:14.704504+00:00
-->
userguide/site/pdf/combined.pdf
+ 0
− 0
View file @ 2ea96130
No preview for this file type
userguide/site/search/search_index.json
+ 1
− 1
View file @ 2ea96130
This diff is collapsed.
userguide/site/sitemap.xml
+ 3
− 3
View file @ 2ea96130
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url>
<loc>None</loc>
<lastmod>2020-11-22</lastmod>
<lastmod>2020-12-11</lastmod>
<changefreq>daily</changefreq>
</url><url>
<loc>None</loc>
<lastmod>2020-11-22</lastmod>
<lastmod>2020-12-11</lastmod>
<changefreq>daily</changefreq>
</url><url>
<loc>None</loc>
<lastmod>2020-11-22</lastmod>
<lastmod>2020-12-11</lastmod>
<changefreq>daily</changefreq>
</url>
</urlset>
\ No newline at end of file
userguide/site/sitemap.xml.gz
+ 0
− 0
View file @ 2ea96130
No preview for this file type
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment