File tree 4 files changed +28
-20
lines changed
docset/winserver2025-ps/smbshare
4 files changed +28
-20
lines changed Original file line number Diff line number Diff line change @@ -187,13 +187,15 @@ Accept wildcard characters: False
187
187
# ## -SkipClientCertificateAccessCheck
188
188
189
189
Specifies whether the server should skip the check for client certificate access when a client
190
- connects. When this parameter is set to `$true`, the server will not perform the access control
191
- checks based on the client certificates. This can be useful in scenarios where the server is acting
192
- as a gateway or proxy, and does not need to perform full certificate validation.
190
+ connects. This parameter only applies when the server certificate mapping
191
+ **RequireClientAuthentication** value is `$true`. When this parameter is set to `$true`, the server
192
+ will not perform the access control checks based on the client certificates. This can be useful in
193
+ scenarios where the server is acting as a gateway or proxy and client certificate validation is
194
+ sufficient.
193
195
194
196
However, it can also increase the risk of security breaches. When this parameter is set to
195
- ` $false` , the server will check whether the client has access to the certificate it presents before
196
- allowing the client to connect.
197
+ ` $false` , the server will perform the access control checks based on the client certificates in
198
+ addition to the client certificate validation before allowing the client to connect.
197
199
198
200
` ` ` yaml
199
201
Type: Boolean[]
Original file line number Diff line number Diff line change @@ -192,13 +192,15 @@ Accept wildcard characters: False
192
192
# ## -SkipClientCertificateAccessCheck
193
193
194
194
Specifies whether the server should skip the check for client certificate access when a client
195
- connects. When this parameter is set to `$true`, the server will not perform the access control
196
- checks based on the client certificates. This can be useful in scenarios where the server is acting
197
- as a gateway or proxy, and does not need to perform full certificate validation.
195
+ connects. This parameter only applies when the server certificate mapping
196
+ **RequireClientAuthentication** value is `$true`. When this parameter is set to `$true`, the server
197
+ will not perform the access control checks based on the client certificates. This can be useful in
198
+ scenarios where the server is acting as a gateway or proxy and client certificate validation is
199
+ sufficient.
198
200
199
201
However, it can also increase the risk of security breaches. When this parameter is set to
200
- ` $false` , the server will check whether the client has access to the certificate it presents before
201
- allowing the client to connect.
202
+ ` $false` , the server will perform the access control checks based on the client certificates in
203
+ addition to the client certificate validation before allowing the client to connect.
202
204
203
205
` ` ` yaml
204
206
Type: Boolean
Original file line number Diff line number Diff line change @@ -252,13 +252,15 @@ Accept wildcard characters: False
252
252
# ## -SkipClientCertificateAccessCheck
253
253
254
254
Specifies whether the server should skip the check for client certificate access when a client
255
- connects. When this parameter is set to `$true`, the server will not perform the access control
256
- checks based on the client certificates. This can be useful in scenarios where the server is acting
257
- as a gateway or proxy, and does not need to perform full certificate validation.
255
+ connects. This parameter only applies when the server certificate mapping
256
+ **RequireClientAuthentication** value is `$true`. When this parameter is set to `$true`, the server
257
+ will not perform the access control checks based on the client certificates. This can be useful in
258
+ scenarios where the server is acting as a gateway or proxy and client certificate validation is
259
+ sufficient.
258
260
259
261
However, it can also increase the risk of security breaches. When this parameter is set to
260
- ` $false` , the server will check whether the client has access to the certificate it presents before
261
- allowing the client to connect.
262
+ ` $false` , the server will perform the access control checks based on the client certificates in
263
+ addition to the client certificate validation before allowing the client to connect.
262
264
263
265
` ` ` yaml
264
266
Type: Boolean[]
Original file line number Diff line number Diff line change @@ -197,13 +197,15 @@ Accept wildcard characters: False
197
197
# ## -SkipClientCertificateAccessCheck
198
198
199
199
Specifies whether the server should skip the check for client certificate access when a client
200
- connects. When this parameter is set to `$true`, the server will not perform the access control
201
- checks based on the client certificates. This can be useful in scenarios where the server is acting
202
- as a gateway or proxy, and does not need to perform full certificate validation.
200
+ connects. This parameter only applies when the server certificate mapping
201
+ **RequireClientAuthentication** value is `$true`. When this parameter is set to `$true`, the server
202
+ will not perform the access control checks based on the client certificates. This can be useful in
203
+ scenarios where the server is acting as a gateway or proxy and client certificate validation is
204
+ sufficient.
203
205
204
206
However, it can also increase the risk of security breaches. When this parameter is set to
205
- ` $false` , the server will check whether the client has access to the certificate it presents before
206
- allowing the client to connect.
207
+ ` $false` , the server will perform the access control checks based on the client certificates in
208
+ addition to the client certificate validation before allowing the client to connect.
207
209
208
210
` ` ` yaml
209
211
Type: Boolean
You can’t perform that action at this time.
0 commit comments