You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/security/authentication/active_directory_authentication.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
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
24
24
25
25
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.
26
26
27
-
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.
27
+
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.
28
28
29
29
### Preparation
30
30
@@ -141,7 +141,7 @@ If this succeeds, you have successfully configured Linux to use Active Directory
141
141
142
142
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.
143
143
144
-
This is actually a relatively simple process, and just requires a configuration tweak in your SSSD configuration file.
144
+
This is a relatively straightforward process, requiring a configuration tweak in your SSSD configuration file.
145
145
146
146
```sh
147
147
[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
199
199
Successfully validated join to domain ad.company.local
200
200
```
201
201
202
-
- Get more advanced informations about the domain:
202
+
- Get more advanced information about the domain:
203
203
204
204
```sh
205
205
[user@host ~]$ adcli info ad.company.local
@@ -269,7 +269,7 @@ Password for user_test:
269
269
270
270
Sometimes, the network service will start after SSSD, that cause trouble with authentication.
271
271
272
-
No AD users will be able to connect until you restarted the service.
272
+
No AD users will be able to connect until you restart the service.
273
273
274
274
In that case, you will have to override the systemd's service file to manage this problem.
0 commit comments