Microsoft Intune supports the use of imported public key pair (PKCS) certificates, commonly used for S/MIME encryption with Email profiles. Certain email profiles in Intune support an option to enable S/MIME where you can define an S/MIME signing certificate and S/MIME encryption cert.
Openssl pkcs12 -in yourfile.pfx -nocerts -out keyfile-encrypted.key What this command does is extract the private key from the.pfx file. Once entered you need to type in the importpassword of the.pfx file. This is the password that you used to protect your keypair when you created your.pfx file.
S/MIME encryption is challenging because email is encrypted with a specific certificate:
Because the same certificate needs to be used across devices, it's not possible to use SCEP or PKCS certificate profiles for this purpose as those certificate delivery mechanisms deliver unique certificates per device.
For more information about using S/MIME with Intune, Use S/MIME to encrypt email.
Intune supports import of PFX certificates for the following platforms:
To use imported PKCS certificates with Intune, you'll need the following infrastructure:
PFX Certificate Connector for Microsoft Intune:
Each Intune tenant supports a single instance of this connector. You can install this connector on the same server as an instance of the Microsoft Intune Certificate connector.
This connector handles requests for PFX files imported to Intune for S/MIME email encryption for a specific user.
This connector can automatically update itself when new versions become available. To use the update capability, you must ensure firewalls are open that allow the connector to contact autoupdate.msappproxy.net on port 443.
For more information, see Network endpoints for Microsoft Intune, and Intune network configuration requirements and bandwidth.
Windows Server:
You use a Windows Server to host the PFX Certificate Connector for Microsoft Intune. The connector is used to process requests for certificates imported to Intune.
The connector requires access to the same ports as detailed for managed devices, as found in our device endpoint content.
Intune supports install of the Microsoft Intune Certificate Connector on the same server as the PFX Certificate Connector for Microsoft Intune.
To support the connector, the server must run .NET 4.6 Framework or higher. If .NET 4.6 Framework isn't installed when you start the installation of the connector, the connector installation will install it automatically.
Visual Studio 2015 or above (optional):
You use Visual Studio to build the helper PowerShell module with cmdlets for importing PFX certificates to Microsoft Intune. To get the helper PowerShell cmdlets, see PFXImport PowerShell Project in GitHub.
When you use Intune to deploy an imported PFX certificate to a user, there are two components at play in addition to the device:
Intune Service: Stores the PFX certificates in an encrypted state and handles the deployment of the certificate to the user device. The passwords protecting the private keys of the certificates are encrypted before they're uploaded using either a hardware security module (HSM) or Windows Cryptography, ensuring that Intune can't access the private key at any time.
PFX Certificate Connector for Microsoft Intune: When a device requests a PFX certificate that was imported to Intune, the encrypted password, the certificate, and the device's public key are sent to the connector. The connector decrypts the password using the on-premises private key, and then re-encrypts the password (and any plist profiles if using iOS) with the device key before sending the certificate back to Intune. Intune then delivers the certificate to the device and the device is able to decrypt it with the device's private key and install the certificate.
Sign in to the Microsoft Endpoint Manager admin center.
Select Tenant administration > Connectors and tokens > Certificate connectors > Add.
Follow the guidance to download the PFX Certificate Connector for Microsoft Intune to a location that's accessible from the server where you're going to install the connector.
After the download completes, sign in to the server and run the installer (PfxCertificateConnectorBootstrapper.exe).
Program FilesMicrosoft IntunePFXCertificateConnector
.The PFX Certificate Connector for Microsoft Intune opens the Enrollment tab after installation. To enable the connection to Intune, Sign In, and enter an account with Azure global administrator or Intune administrator permissions.
Warning
By default, in Windows Server IE Enhanced Security Configuration is set to On which can cause issues with the sign-in to Office 365.
Close the window.
In the Microsoft Endpoint Manager admin center, go back to Tenant administration > Connectors and tokens > Certificate connectors. In a few moments, a green check mark appears and the connection status updates. The connector server can now communicate with Intune.
You use Microsoft Graph to import your users PFX certificates into Intune. The helper PFXImport PowerShell Project at GitHub provides you with cmdlets to do the operations with ease.
If you prefer to use your own custom solution using Graph, use the userPFXCertificate resource type.
To make use of the PowerShell cmdlets, you build the project yourself using Visual Studio. The process is straight forward and while it can run on the server, we recommended you run it on your workstation.
Go to the root of the Intune-Resource-Access repository on GitHub, and then either download or clone the repository with Git to your machine.
Go to .Intune-Resource-Access-developsrcPFXImportPowershell
and open the project with Visual Studio using the file PFXImportPS.sln.
On the top, change from Debug to Release.
Go to Build and select Build PFXImportPS. After a few moments you'll see the Build succeeded confirmation appear at the bottom left of Visual Studio.
The build process creates a new folder with the PowerShell Module at .Intune-Resource-Access-developsrcPFXImportPowershellPFXImportPSbinRelease
.
You'll use this Release folder for the next steps.
You import PFX Certificates and their private keys to Intune. The password protecting the private key is encrypted with a public key that is stored on-premises. You can use either Windows cryptography, a hardware security module, or another type of cryptography to generate and store the public/private key pairs. Depending on the type of cryptography used, the public/private key pair can be exported in a file format for backup purposes.
Dec 05, 2018 Universal Serial key Generator Full Version Free Download Here. Universal Keygen Generator 2019 is just not a simple program it is a smart level utility which used to create the keygen file for any software program. Now with the help of this program, the designing of keys and users name for any software is not a difficult job. Download Serial Key Generator from official sites for free using QPDownload.com. Additional information about license you can found on owners sites. How do I access the free Serial Key Generator download for PC? Just click the free Serial Key Generator download button at the top left of the page. Clicking this link will start the. Mar 04, 2019 The Universal keygen generator Full Download will prove very helpful for all and sundry, it is affordable, fast and efficient, and most importantly to all geeks – non-restrictive! Features of Universal Keygen Generator Latest 2020. TheUniversal keygen generator 2019 is a public key that can use for any application entirely; It has no charges. The 7.0 version of Serial Key Generator is available as a free download on our software library. The actual developer of the software is VCL Examples. The latest version of Serial Key Generator can be installed on PCs running Windows XP/Vista/7/8/10, 32-bit. Our antivirus scan shows that this download is. Jan 19, 2020 Universal Keygen Generator 2019 Free Download Full Version. Universal Keygen Generator 2020 For PC Windows/Mac. Serial Key Generator is a simple and convenient program whose functionality is focused on generating unique serial keys in any quantity. The user is only required to set the basic settings and start the creation process. Cd key generator free download for pc.
The PowerShell module provides methods to create a key using Windows cryptography. You can also use other tools to create a key.
Copy the Release folder that's created by Visual Studio to the server where you installed the PFX Certificate Connector for Microsoft Intune. This folder contains the PowerShell module.
On the server, open PowerShell as an Administrator and then navigate to the Release folder that contains the PowerShell module.
To import the module, run Import-Module .IntunePfxImport.psd1
to import the module.
Next, run Add-IntuneKspKey 'Microsoft Software Key Storage Provider' 'PFXEncryptionKey'
Tip
The provider you use must be selected again when you import PFX Certificates. You can use the Microsoft Software Key Storage Provider, although it is supported to use a different provider. The key name is also provided as an example, and you can use a different key name of your choice.
If you plan to import the certificate from your workstation, you can export this key to a file with the following command:Export-IntunePublicKey -ProviderName '<ProviderName>' -KeyName '<KeyName>' -FilePath '<File pathFilename.PFX>'
The private key must be imported on the server that hosts the PFX Certificate Connector for Microsoft Intune so that imported PFX certificates can be processed successfully.
You can use a hardware security module (HSM) to generate and store the public/private key pair. For more information, see the HSM provider's documentation.
The following process uses the PowerShell cmdlets as an example of how to import the PFX certificates. You can pick different options depending on your requirements.
Options include:
Intended Purpose (groups certificates together based on a tag):
Padding Scheme:
Select the Key Storage Provider that matches the provider you used to create the key.
Export the certificates from any Certification Authority (CA) by following the documentation from the provider. For Microsoft Active Directory Certificate Services, you can use this sample script.
On the server, open PowerShell as an Administrator and then navigate to the Release folder that contains the PowerShell module.
To import the module, run Import-Module .IntunePfxImport.psd1
To authenticate to Intune Graph, run $authResult = Get-IntuneAuthenticationToken -AdminUserName '<Admin-UPN>'
Note
As the authentication is run against Graph, you must provide permissions to the AppID. If it's the first time you've used this utility, a Global administrator is required. The PowerShell cmdlets use the same AppID as the one used with PowerShell Intune Samples.
Convert the password for each PFX file your are importing to a secure string by running $SecureFilePassword = ConvertTo-SecureString -String '<PFXPassword>' -AsPlainText -Force
.
To create a UserPFXCertificate object, run$userPFXObject = New-IntuneUserPfxCertificate -PathToPfxFile '<FullPathPFXToCert>' $SecureFilePassword '<UserUPN>' '<ProviderName>' '<KeyName>' '<IntendedPurpose>'
For example: $userPFXObject = New-IntuneUserPfxCertificate -PathToPfxFile 'C:tempuserA.pfx' $SecureFilePassword '[email protected]' 'Microsoft Software Key Storage Provider' 'PFXEncryptionKey' 'smimeEncryption'
Note
When you import the certificate from a system other than the server where the connector is installed, use must use the following command that includes the key file path: $userPFXObject = New-IntuneUserPfxCertificate -PathToPfxFile '<FullPathPFXToCert>' $SecureFilePassword '<UserUPN>' '<ProviderName>' '<KeyName>' '<IntendedPurpose>' '<PaddingScheme>' '<File path to public key file>'
Import the UserPFXCertificate object to Intune by running Import-IntuneUserPfxCertificate -AuthenticationResult $authResult -CertificateList $userPFXObject
To validate the certificate was imported, run Get-IntuneUserPfxCertificate -AuthenticationResult $authResult -UserList '<UserUPN>'
For more information about other available commands, see the readme file at PFXImport PowerShell Project at GitHub.
After importing the certificates to Intune, create a PKCS imported certificate profile, and assign it to Azure Active Directory groups.
Sign in to the Microsoft Endpoint Manager admin center.
Select and go to Devices > Configuration profiles > Create profile.
Enter the following properties:
Select Create.
In Basics, enter the following properties:
Select Next.
In Configuration settings, enter the following properties:
Select Next.
In Scope tags (optional), assign a tag to filter the profile to specific IT groups, such as US-NC IT Team
or JohnGlenn_ITDepartment
. For more information about scope tags, see Use RBAC and scope tags for distributed IT.
Select Next.
In Assignments, select the user or groups that will receive your profile. For more information on assigning profiles, see Assign user and device profiles.
Select Next.
(Applies to Windows 10 only) In Applicability Rules, specify applicability rules to refine the assignment of this profile. You can choose to assign or not assign the profile based on the OS edition or version of a device.
For more information, see Applicability rules in Create a device profile in Microsoft Intune.
Select Next.
In Review + create, review your settings. When you select Create, your changes are saved, and the profile is assigned. The policy is also shown in the profiles list.
The following partners provide supported methods or tools you can use to import PFX certificates to Intune.
If you use the DigiCert PKI Platform service, you can use the DigiCert Import Tool for Intune S/MIME Certificates to import PFX certificates to Intune. Use of this tool replaces the need to follow the instructions in the section Import PFX Certificates to Intune that's detailed earlier in this article.
To learn more about the DigiCert Import tool, including how to obtain the tool, see https://knowledge.digicert.com/tutorials/microsoft-intune.html in the DigiCert knowledge base.
The profile is created, but it's not doing anything yet. Assign the new device profile.
If you need to move or copy a certificate from Windows IIS6 to Linux Apache server (or other device requiring .key and .crt formats) perform following steps:
1. Export IIS6 certificate into into .pfx format
On Windows Server machine
Start > Run MMC
File > Add/Remove Snap-in
Add > Certificates > Add > Computer Account > Local Computer
Navigate to Certificates > Personal > Certificates
Right click your certificate > All Tasks > Export
Yes, export private key
Personal Information Exchange (.pfx) - clear all checkboxes
leave password blank
Choose where to save file
Finish
2 . Extract private key and certificate file
You need OpenSSL to extract private key and certificate from .pfx
If you have Linux web server in place you should already have openssl there.
Alternatively you can download and install Windows version. For more info and latest versions check here
If you installed Windows version run openssl.exe from C:OpenSSL-Win32bin
In Linux version just type openssl in terminal
in OpenSSL
Export private key and certificate:
pkcs12 -in 'C:yourpathfilename.pfx' -out 'C:yourpathcert.pem'
Enter Import Password: leave blank
Enter PEM pass phrase: 1234 (or anything else)
Created cert.pem file will have encrypted private key and all certificates (identity, root, intermediate) in a plain text.
To extract certificates or encrypted private key just open cert.pem in a text editor and copy required parts to a new .crt or .key file. If formatting doesn't look right in Windows notepad use Notepad++ or similar text editor.
If you need private key in not encrypted format you can extract it from cert.pem removing encryption:
rsa -in 'C:yourpathcert.pem' -out 'C:yourpathPrivateKey.key'
Enter pass phrase (1234 or somethinkg else you set previously) to remove encryption.
Windows Server 2003
IIS6
OpenSSL