-
Notifications
You must be signed in to change notification settings - Fork 310
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
# minor corrections -
active_directory_authentication.md
(#1436)
- Loading branch information
1 parent
6ab2cb4
commit 15cdd29
Showing
1 changed file
with
4 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,7 +24,7 @@ This guide, however, will just cover configuring authentication against Active D | |
|
||
The domain name `ad.company.local` throughout this guide will represent the Active Directory domain. To follow this guide, replace it with your AD domain's actual domain name. | ||
|
||
The first step along the way to join a Linux system into AD is to discover your AD cluster, to ensure that the network configuration is correct on both sides. | ||
The first step to joining a Linux system into AD is to discover your AD cluster, to ensure the network configuration is correct on both sides. | ||
|
||
### Preparation | ||
|
||
|
@@ -141,7 +141,7 @@ If this succeeds, you have successfully configured Linux to use Active Directory | |
|
||
In a completely default setup, you will need to log in with your AD account by specifying the domain in your username (e.g., `[email protected]`). If this is not the desired behavior, and you instead want to be able to omit the domain name at authentication time, you can configure SSSD to default to a specific domain. | ||
|
||
This is actually a relatively simple process, and just requires a configuration tweak in your SSSD configuration file. | ||
This is a relatively straightforward process, requiring a configuration tweak in your SSSD configuration file. | ||
|
||
```sh | ||
[user@host ~]$ sudo vi /etc/sssd/sssd.conf | ||
|
@@ -199,7 +199,7 @@ Now, only users from group1 and group2, or user1 and user2 will be able to conne | |
Successfully validated join to domain ad.company.local | ||
``` | ||
|
||
- Get more advanced informations about the domain: | ||
- Get more advanced information about the domain: | ||
|
||
```sh | ||
[user@host ~]$ adcli info ad.company.local | ||
|
@@ -269,7 +269,7 @@ Password for user_test: | |
Sometimes, the network service will start after SSSD, that cause trouble with authentication. | ||
No AD users will be able to connect until you restarted the service. | ||
No AD users will be able to connect until you restart the service. | ||
In that case, you will have to override the systemd's service file to manage this problem. | ||
|
||
|