Skip to content

Commit 8427426

Browse files
committed
Applied PM/Dev feedback
1 parent bcab8e5 commit 8427426

4 files changed

+28
-20
lines changed

docset/winserver2022-ps/smbshare/Get-SmbServerCertificateMapping.md

+7-5
Original file line numberDiff line numberDiff line change
@@ -190,13 +190,15 @@ Accept wildcard characters: False
190190
### -SkipClientCertificateAccessCheck
191191

192192
Specifies whether the server should skip the check for client certificate access when a client
193-
connects. When this parameter is set to `$true`, the server will not perform the access control
194-
checks based on the client certificates. This can be useful in scenarios where the server is acting
195-
as a gateway or proxy, and does not need to perform full certificate validation.
193+
connects. This parameter only applies when the server certificate mapping
194+
**RequireClientAuthentication** value is `$true`. When this parameter is set to `$true`, the server
195+
will not perform the access control checks based on the client certificates. This can be useful in
196+
scenarios where the server is acting as a gateway or proxy and client certificate validation is
197+
sufficient.
196198

197199
However, it can also increase the risk of security breaches. When this parameter is set to
198-
`$false`, the server will check whether the client has access to the certificate it presents before
199-
allowing the client to connect.
200+
`$false`, the server will perform the access control checks based on the client certificates in
201+
addition to the client certificate validation before allowing the client to connect.
200202

201203
```yaml
202204
Type: Boolean[]

docset/winserver2022-ps/smbshare/New-SmbServerCertificateMapping.md

+7-5
Original file line numberDiff line numberDiff line change
@@ -195,13 +195,15 @@ Accept wildcard characters: False
195195
### -SkipClientCertificateAccessCheck
196196

197197
Specifies whether the server should skip the check for client certificate access when a client
198-
connects. When this parameter is set to `$true`, the server will not perform the access control
199-
checks based on the client certificates. This can be useful in scenarios where the server is acting
200-
as a gateway or proxy, and does not need to perform full certificate validation.
198+
connects. This parameter only applies when the server certificate mapping
199+
**RequireClientAuthentication** value is `$true`. When this parameter is set to `$true`, the server
200+
will not perform the access control checks based on the client certificates. This can be useful in
201+
scenarios where the server is acting as a gateway or proxy and client certificate validation is
202+
sufficient.
201203

202204
However, it can also increase the risk of security breaches. When this parameter is set to
203-
`$false`, the server will check whether the client has access to the certificate it presents before
204-
allowing the client to connect.
205+
`$false`, the server will perform the access control checks based on the client certificates in
206+
addition to the client certificate validation before allowing the client to connect.
205207

206208
```yaml
207209
Type: Boolean

docset/winserver2022-ps/smbshare/Remove-SmbServerCertificateMapping.md

+7-5
Original file line numberDiff line numberDiff line change
@@ -255,13 +255,15 @@ Accept wildcard characters: False
255255
### -SkipClientCertificateAccessCheck
256256

257257
Specifies whether the server should skip the check for client certificate access when a client
258-
connects. When this parameter is set to `$true`, the server will not perform the access control
259-
checks based on the client certificates. This can be useful in scenarios where the server is acting
260-
as a gateway or proxy, and does not need to perform full certificate validation.
258+
connects. This parameter only applies when the server certificate mapping
259+
**RequireClientAuthentication** value is `$true`. When this parameter is set to `$true`, the server
260+
will not perform the access control checks based on the client certificates. This can be useful in
261+
scenarios where the server is acting as a gateway or proxy and client certificate validation is
262+
sufficient.
261263

262264
However, it can also increase the risk of security breaches. When this parameter is set to
263-
`$false`, the server will check whether the client has access to the certificate it presents before
264-
allowing the client to connect.
265+
`$false`, the server will perform the access control checks based on the client certificates in
266+
addition to the client certificate validation before allowing the client to connect.
265267

266268
```yaml
267269
Type: Boolean[]

docset/winserver2022-ps/smbshare/Set-SmbServerCertificateMapping.md

+7-5
Original file line numberDiff line numberDiff line change
@@ -200,13 +200,15 @@ Accept wildcard characters: False
200200
### -SkipClientCertificateAccessCheck
201201

202202
Specifies whether the server should skip the check for client certificate access when a client
203-
connects. When this parameter is set to `$true`, the server will not perform the access control
204-
checks based on the client certificates. This can be useful in scenarios where the server is acting
205-
as a gateway or proxy, and does not need to perform full certificate validation.
203+
connects. This parameter only applies when the server certificate mapping
204+
**RequireClientAuthentication** value is `$true`. When this parameter is set to `$true`, the server
205+
will not perform the access control checks based on the client certificates. This can be useful in
206+
scenarios where the server is acting as a gateway or proxy and client certificate validation is
207+
sufficient.
206208

207209
However, it can also increase the risk of security breaches. When this parameter is set to
208-
`$false`, the server will check whether the client has access to the certificate it presents before
209-
allowing the client to connect.
210+
`$false`, the server will perform the access control checks based on the client certificates in
211+
addition to the client certificate validation before allowing the client to connect.
210212

211213
```yaml
212214
Type: Boolean

0 commit comments

Comments
 (0)