{"id":542,"date":"2019-10-08T20:03:38","date_gmt":"2019-10-09T00:03:38","guid":{"rendered":"https:\/\/blog.mzimmerer.com\/?p=542"},"modified":"2019-10-08T20:04:03","modified_gmt":"2019-10-09T00:04:03","slug":"mac-apple-ios-devices-on-802-11x-with-nps","status":"publish","type":"post","link":"https:\/\/blog.mzimmerer.com\/?p=542","title":{"rendered":"Mac\/Apple iOS devices on 802.11x with NPS"},"content":{"rendered":"\n

I was having a conversation on reddit about setting up apple devices on certificate based 802.11x over a year ago and since then, I’ve received quite a few PM’s asking for details or instructions. I’ve been meaning to throw the internal instructions I wrote up into a sanitized blog post to start referring people to. Welp, this is it. Straight to the point and more like a how-to. This is assuming the NPS server is already up and running.<\/p>\n\n\n\n

Windows Server NPS RADIUS certificate based authentication pre-reqs<\/h2>\n\n\n\n

A Certificate Template for the Apple Devices has to be created.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The most important setting here is that the Subject Name will be supplied in the request<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When Apple Devices attempt to authenticate to 802.11x, they will use their Machine or Hostname but present it as an LDAP user. This is not something we can change. The setting above allows this action. In addition, that Machine or Hostname must be found in Active Directory. An OU can be created for these machines.<\/strong><\/p>\n\n\n\n

In that OU, A USER Account must be created for each Apple Device and that user must be associated with the appropriate Certificate as well as have the same username as the devices hostname. This is detailed in the How-To instructions, but see example below.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

It’s a good idea to also create a Group Policy that prevents login from these accounts.<\/strong><\/p>\n\n\n\n

How To<\/h2>\n\n\n\n

To add an Apple Device to the wifi, first we need to\ncreate, sign, and export a Certificate.<\/strong><\/p>\n\n\n\n

Run mmc.exe as Administrator on your workstation. Once\nopen, click File -> Add Remove Snap-ins.<\/strong><\/p>\n\n\n\n

Select Certificates from the list and specify Computer Account,<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Click Next and select Local computer,<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Click Finish and then Click OK to close the Add or\nRemove Snap-ins Window.<\/strong><\/p>\n\n\n\n

Expand Certificates (Local Computer), Then Personal.<\/strong><\/p>\n\n\n\n

Right Click Certificates and select All Tasks and then Request New Certificate as seen below.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Click next to skip the “Before you Begin” window and ensure on the next page, Active Directory Enrollment Policy is selected as seen below and select Next.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The next page will allow you select which type of Certificate you would like to request. We want the Apple Device Wifi Certificate. Follow the Prompt and click the Blue Alert to Configure settings.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The only bit that needs configured is that we need to Add a “Common Name”. This should match the Machine or Hostname of the target Apple Device. <\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If you’re unsure of the hostname, open a terminal on the Apple device. Note that the hostname is displayed. To verify, use the hostname command to display the full name. We do not need the TLD, only the first bit of the response.<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

Once complete and Properties window is closed, the Alert should be gone. Click the Checkbox for the Apple Device Wifi Certificate and click Enroll.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The response should be STATUS: Enrollment Pending<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Navigate to the Certificate Authority Snap-in via MMC, or RDP to the server directly to access it.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You will see the Certificate request that you\nsubmitted from your workstation. The Request Common Name should again, match\nthe hostname of the target Device.<\/strong><\/p>\n\n\n\n

Right click the request and select, All Tasks -> Issue.<\/strong><\/p>\n\n\n\n

Back to the local MMC, right click the Certificates root and navigate to All Tasks -> Automatically Enroll and Retrieve Certificates<\/strong><\/p>\n\n\n\n

(If the Certificate Auto-Enrollment GPO is not applied to your workstation this does not work!)<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Wizard will reflect how many Certificates are pending approval, ensure any or all are selected and click Enroll. The result should show Succeeded at the end of the Wizard<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Note I had some test Certificates that I had denied. You should see no denials.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

With this complete we should now see the certificate in your Personal Certificate folder as seen below\u2026<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Next step is to export the certificate. Right\nClick it, select All Tasks -> Export\u2026<\/strong><\/p>\n\n\n\n

The wizard will open.<\/strong><\/p>\n\n\n\n

Do this twice. Once with exporting the private key, once without.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When exporting without the key, the format will be DER\nencoded binary or .CER<\/strong><\/p>\n\n\n\n

When with the key, it should reflect what is below.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You must password protect the key. This password will be needed later when configuring the device!<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When you save it, make sure you specify which has the Private Key included and which doesn’t.<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

Before taking these Certificates to the target device,\nwe need to create and entry in AD and map the new certificate to that entry.<\/strong><\/p>\n\n\n\n

Open Active Directory and navigate to the OU you created.<\/strong><\/p>\n\n\n\n

Create a new USER within this OU.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The user logon name must match the Apple Device Hostname.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Generate a SECURE PASSWORD. There is no need to record\nthis information, in fact it should be disposed of.<\/strong><\/p>\n\n\n\n

Set options as seen below.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Proceed to finish the wizard.<\/strong><\/p>\n\n\n\n

Select View and Advanced Features within AD\u2026<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Returning to the OU with the new user, Right Click the\nuser and select Name Mappings.<\/strong><\/p>\n\n\n\n

Click Add and select the appropriate Certificate WITH\nOUT the Private Key.<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Selecting the certificate and clicking OK will result in the following<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Click OK to proceed, then Apply and OK to complete the\ntask.<\/strong><\/p>\n\n\n\n

Lastly, the new user should be added to a Security Group that prevents login or other network access.<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

Wrap up<\/h2>\n\n\n\n

That’s about it. The last step is installing the certificate with the key to the client machine and configuring the network there. I’m not going to bother touching on that, I feel there’s plenty of resources on the web for installing an 802.11x cert on a mac once it’s created.<\/p>\n\n\n\n

I hope this helps, goodluck.<\/p>\n","protected":false},"excerpt":{"rendered":"

I was having a conversation on reddit about setting up apple devices on certificate based 802.11x over a year ago and since then, I’ve received quite a few PM’s asking for details or instructions. I’ve been meaning to throw the internal instructions I wrote up into a sanitized blog post…<\/p>\n

Continue readingMac\/Apple iOS devices on 802.11x with NPS<\/span><\/a><\/div>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,6,1],"tags":[],"class_list":["post-542","post","type-post","status-publish","format-standard","hentry","category-misc","category-networking","category-uncategorized","entry"],"_links":{"self":[{"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=\/wp\/v2\/posts\/542","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=542"}],"version-history":[{"count":3,"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=\/wp\/v2\/posts\/542\/revisions"}],"predecessor-version":[{"id":572,"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=\/wp\/v2\/posts\/542\/revisions\/572"}],"wp:attachment":[{"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=542"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=542"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mzimmerer.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=542"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}