@@ -25,7 +25,7 @@ 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):
<palign="center">
<imgsrc="../img/map.png"alt="Create an admin account"style="height:250px;width:600px"/>
<imgsrc="../img/map.png"alt="Create an admin account"style="height:400px;"/>
</p>
The IP 10.10.0.1 is random, and should be seen as an example.
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.
...
...
@@ -31,13 +31,13 @@ The **Jami Account Management Server URL** in this case would be the DNS address
Open Jami, go to the login page. Click on "Advanced":
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.
...
...
@@ -47,13 +47,13 @@ The **Jami Account Management Server URL** in this case would be the DNS address
Open Jami, go to the login page. Click on "Advanced":
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.
...
...
@@ -63,13 +63,13 @@ The **Jami Account Management Server URL** in this case would be the DNS address
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.
...
...
@@ -77,13 +77,13 @@ The server in this case would be the DNS address of your server and the username
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.
@@ -64,7 +64,7 @@ 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" />
<img src="img/step1.png" alt="Create an admin account" style="height:400px;"/>
</p>
...
...
@@ -75,8 +75,8 @@ 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" />
<img src="img/step2-2.png" alt="Create an admin account" />
<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>
...
...
@@ -101,7 +101,7 @@ 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" />
<img src="img/ldap.png" style="height:400px;"/>
</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:
...
...
@@ -124,7 +124,7 @@ If your company provides you with Active Directory for user management, you will
<p align="center">
<img src="img/ad.png" />
<img src="img/ad.png" style="height:400px;"/>
</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:
...
...
@@ -145,7 +145,7 @@ 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" />
<img src="img/local.png" style="height:400px;"/>
</p>
**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.
...
...
@@ -155,7 +155,7 @@ 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" />
<img src="img/step4.png" style="height:400px;"/>
</p>
| Parameter | Details |
...
...
@@ -174,7 +174,7 @@ Click on "Set Server Parameters" to finalize the configuration.
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"
