![]() ![]() Paste in the contents of your CSR from step 4 into the CSR text field.Complete the following steps in the Create Certificate from CSR prompt:.Select Management Certificate Template > Create Certificate from CSR.Navigate to Settings > Global Management > PKI Certificates.In Jamf Pro navigate to PKI Certificates to create a certificate from the CSR file:.Open the Certificate Signing Request (CSR) file in TextEdit (or your preferred text editor) and copy the entire contents (including -BEGIN CERTIFICATE REQUEST- and -END CERTIFICATE REQUEST-) to the clipboard.Select the Done button in the Certificate Assistant window.Set a File Name in the Save As field and a directory to save the file in the Where drop down menu, and then select the Save button.Select the Saved to disk radio button from the Request is option.Note: The User Email Address and Common Name fields will appear in the Certificate in System Preferences > Profiles when deployed to the device.Enter a User Email Address and Common Name.Complete the following steps in the Certificate Assistant prompt:.Select the Keychain Access menu item from the menu bar and select Certificate Assistant > Request a Certificate From a Certificate Authority.Open the Keychain Access app from Applications > Utilities.Detailed instruction on Creating a Configuration Profile for macOS is available in the Absolute Secure Access System Administrator Guide Note: An example VPN payload in Apple Configurator is pictured below. ![]() Create a Profile that includes a VPN payload configured for Absolute Secure Access using Apple Configurator.Signing the Profile makes the payload configurations read only allowing the configuration to take place exactly as it would if applied via Apple Configurator. The workaround is to create a Profile with the necessary payloads in Apple Configurator, and then sign the profile before uploading it into Jamf Pro. Fix SummaryĪ workaround has been established by Jamf to remediate this issue while they work to correct the issue in Jamf Pro. When fixed, Product Issues are listed as Bug Fixes in Jamf Release Notes. Jamf has opened a Product Issue related to this: PI-009939. This is causing the Custom SSL VPN payload in the profile to not apply properly when distributed via Jamf Pro to a macOS device. Jamf Pro has a known issue whereby Jamf’s server-side software is not yet equipped to handle some keys causing the addition and removal of keys within a Custom SSL VPN payload. However, the VPN connection toggle in the Absolute Secure Access Client will not toggle on. The VPN payload is delivered, and the Absolute Secure Access Client appears to be configured. Absolute Secure Access Custom SSL VPN payloads are not applying properly when distributed with Jamf Pro. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |