mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
Added missing periods
This commit is contained in:
parent
aa350b74fe
commit
997820ed16
@ -43,7 +43,7 @@ Applications installed using WMI classes are not removed when the MDM account is
|
|||||||
|
|
||||||
### Passing CDATA in SyncML does not work
|
### Passing CDATA in SyncML does not work
|
||||||
|
|
||||||
Passing CDATA in data in SyncML to ConfigManager and CSPs does not work in Windows 10 and Windows 11
|
Passing CDATA in data in SyncML to ConfigManager and CSPs does not work in Windows 10 and Windows 11.
|
||||||
|
|
||||||
### SSL settings in IIS server for SCEP must be set to "Ignore"
|
### SSL settings in IIS server for SCEP must be set to "Ignore"
|
||||||
|
|
||||||
@ -85,25 +85,25 @@ EAP XML must be updated with relevant information for your environment This can
|
|||||||
- For Wi-Fi, look for the <EAPConfig> section of your current WLAN Profile XML (This is what you specify for the WLanXml node in the Wi-Fi CSP). Within these tags you will find the complete EAP configuration. Replace the section under <EAPConfig> with your updated XML and update your Wi-Fi profile. You might need to refer to your MDM’s guidance on how to deploy a new Wi-Fi profile.
|
- For Wi-Fi, look for the <EAPConfig> section of your current WLAN Profile XML (This is what you specify for the WLanXml node in the Wi-Fi CSP). Within these tags you will find the complete EAP configuration. Replace the section under <EAPConfig> with your updated XML and update your Wi-Fi profile. You might need to refer to your MDM’s guidance on how to deploy a new Wi-Fi profile.
|
||||||
- For VPN, EAP Configuration is a separate field in the MDM Configuration. Work with your MDM provider to identify and update the appropriate Field.
|
- For VPN, EAP Configuration is a separate field in the MDM Configuration. Work with your MDM provider to identify and update the appropriate Field.
|
||||||
|
|
||||||
For information about EAP Settings, see <https://technet.microsoft.com/library/hh945104.aspx#BKMK_Cfg_cert_Selct>
|
For information about EAP Settings, see <https://technet.microsoft.com/library/hh945104.aspx#BKMK_Cfg_cert_Selct>.
|
||||||
|
|
||||||
For information about generating an EAP XML, see [EAP configuration](eap-configuration.md)
|
For information about generating an EAP XML, see [EAP configuration](eap-configuration.md).
|
||||||
|
|
||||||
For more information about extended key usage, see <http://tools.ietf.org/html/rfc5280#section-4.2.1.12>
|
For more information about extended key usage, see <http://tools.ietf.org/html/rfc5280#section-4.2.1.12>.
|
||||||
|
|
||||||
For information about adding extended key usage (EKU) to a certificate, see <https://technet.microsoft.com/library/cc731792.aspx>
|
For information about adding extended key usage (EKU) to a certificate, see <https://technet.microsoft.com/library/cc731792.aspx>.
|
||||||
|
|
||||||
The following list describes the prerequisites for a certificate to be used with EAP:
|
The following list describes the prerequisites for a certificate to be used with EAP:
|
||||||
|
|
||||||
- The certificate must have at least one of the following EKU (Extended Key Usage) properties:
|
- The certificate must have at least one of the following EKU (Extended Key Usage) properties:
|
||||||
|
|
||||||
- Client Authentication
|
- Client Authentication.
|
||||||
- As defined by RFC 5280, this is a well-defined OID with Value 1.3.6.1.5.5.7.3.2
|
- As defined by RFC 5280, this is a well-defined OID with Value 1.3.6.1.5.5.7.3.2.
|
||||||
- Any Purpose
|
- Any Purpose.
|
||||||
- An EKU Defined and published by Microsoft, is a well-defined OID with value 1.3.6.1.4.1.311.10.12.1. The inclusion of this OID implies that the certificate can be used for any purpose. The advantage of this EKU over the All Purpose EKU is that additional non-critical or custom EKUs can still be added to the certificate for effective filtering.
|
- An EKU Defined and published by Microsoft, is a well-defined OID with value 1.3.6.1.4.1.311.10.12.1. The inclusion of this OID implies that the certificate can be used for any purpose. The advantage of this EKU over the All Purpose EKU is that additional non-critical or custom EKUs can still be added to the certificate for effective filtering.
|
||||||
- All Purpose
|
- All Purpose.
|
||||||
- As defined by RFC 5280, If a CA includes extended key usages to satisfy some application needs, but does not want to restrict usage of the key, the CA can add an Extended Key Usage Value of 0. A certificate with such an EKU can be used for all purposes.
|
- As defined by RFC 5280, If a CA includes extended key usages to satisfy some application needs, but does not want to restrict usage of the key, the CA can add an Extended Key Usage Value of 0. A certificate with such an EKU can be used for all purposes.
|
||||||
- The user or the computer certificate on the client chains to a trusted root CA
|
- The user or the computer certificate on the client chains to a trusted root CA.
|
||||||
- The user or the computer certificate does not fail any one of the checks that are performed by the CryptoAPI certificate store, and the certificate passes requirements in the remote access policy.
|
- The user or the computer certificate does not fail any one of the checks that are performed by the CryptoAPI certificate store, and the certificate passes requirements in the remote access policy.
|
||||||
- The user or the computer certificate does not fail any one of the certificate object identifier checks that are specified in the Internet Authentication Service (IAS)/Radius Server.
|
- The user or the computer certificate does not fail any one of the certificate object identifier checks that are specified in the Internet Authentication Service (IAS)/Radius Server.
|
||||||
- The Subject Alternative Name (SubjectAltName) extension in the certificate contains the user principal name (UPN) of the user.
|
- The Subject Alternative Name (SubjectAltName) extension in the certificate contains the user principal name (UPN) of the user.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user