jami
/
jami-docs
mirror of https://git.jami.net/savoirfairelinux/jami-docs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

jams/index.md: table, additional guides order, below → following 

Update pure HTML tables to show code formatting
`…` → <code>…</code>

Admin guide, then client guide as:
* It will be the same order as the JAMS manual PDF, and
* Admin needs to be set up before clients are set up.

If printed, it may not be below, it may be on the next page.
Following includes below and next.

Change-Id: Ib41303626409cac54c963093bae18211d533cd18
This commit is contained in:
ovari123 2025-01-27 21:13:04 -04:00 committed by Adrien Béraud
parent 0c8428362f
commit e22dac56e2
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
jams/index.md
View File

@ -16,8 +16,8 @@ Downloadable JAMS manuals:
```{toctree}
:maxdepth: 1
client
admin
client
```
## Introduction
@ -86,7 +86,7 @@ In order to be completely secure, JAMS does not generate certificates for device
JAMS instead issues certificates based on a certificate signing request sent to it by the device.
This therefore removes the requirement to send a private key over the wire.
The diagram below shows the entire process of how a device enrolls with JAMS:
The following diagram shows the entire process of how a device enrolls with JAMS:
![«Image: Device enrollment»](images/device_enroll.png "Device enrollment")
@ -210,7 +210,7 @@ If the enterprise provides an LDAP directory for user management, it is required
![«Image: JAMS: Lightweight Directory Access Protocol (LDAP)»](images/jams-ldap.png "JAMS: Lightweight Directory Access Protocol (LDAP)")
The admin should provide most of the required information; however, below is a detailed overview of each field:
The admin should provide most of the required information; however, the following is a detailed overview of each field:
<table>
<thead>
@ -244,18 +244,20 @@ The admin should provide most of the required information; however, below is a d
</tr>
<tr>
<td><strong>BaseDN</strong></td>
<td>The base realm where the user accounts are located; in most cases, it is `ou=users,dc=enterprise,dc=org`.</td>
<td>The base realm where the user accounts are located; in most cases, it is <code>ou=users,dc=enterprise,dc=org</code>.</td>
</tr>
</tbody>
</table>
<br>
#### Option 2: Microsoft Active Directory (AD)
If the enterprise provides Active Directory (AD) for user management, it is required to know its access information and an automated account that has read-only rights to do use look-ups.
![«Image: JAMS: Active Directory (AD)»](images/jams-ad.png "JAMS: Active Directory (AD)")
The admin should provide most of the required information; however, below is a detailed overview of each field:
The admin should provide most of the required information; however, the following is a detailed overview of each field:
<table>
<thead>