Anyone using PEAP-MSCHAPv2 with Jamf Connect Login?

[nwsbear]

Is it possible? Out of the box, when choosing said PEAP network from the Network Connection dialog in JCL, nothing happens when entering AD credentials. Network works perfectly fine within OS. Machines not domain bound.

Thanks

[d_mccullough]

We are experiencing similar behavior.

Over a hotspot, JCL works fine. When connected to a PEAP network it never even tries to join.

[nwsbear]

Heck- let's simplify it. What about simply using RADIUS/NPS/Windows PKI at all (forget pre-login). We'd like to have users connect without manually entering credentials- maybe with some kind of user cert? We're using Jamf Connect Login/Verify, so local Mac usernames/passwords are the same as AD credentials. Machines are not AD bound. Also- we have the Jamf ADCS Connector configured to issue certs (not any that will work at this point).

Our ultimate goal is to have our Macs be the only devices allowed on our corporate network. We could continue to use PEAP-MSCHAPv2, but that allows any device to connect if you have valid AD credentials.