Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WiFi Profile for IOS not working Properly - Password Issue

I'm trying to push a WiFI Profile to an IOS device (Apple iPhone).  The profile is set to "Corporate WPA/WPA2" and includes EAP settings, as our WAP's use PEAP to communicate to our RADIUS server for authentication.    The profile goes on the device, but when I select to join the network it prompts for a password.  If I put the password in, it works, but I want it to happen seamlessly.   Now, I have a working IOS profile from a looooong time ago, using the IPhone Configuration Utility (before they got rid of it in Windows), so I compared the .mobileconfig file from that one to the one I just made (exported from SMC) and I noticed one difference:

In the original, working profile, there is a value called "UserPassword" under the "EAPClientConfiguration" dictionary, that contains the password.   HOWEVER, in the newly created profile from SMC 6.1.8, it puts the password in the main dictionary under the "Password" value.    If I modify the new profile with a text editor and move the value and change the name to where it was in the old one, then reimport it, it works.    

I was going to just call it good, but it would be nice to have it working properly in SMC so I can make changes to the profile directly, instead of having to export the thing.

I guess i'm posting this as a bug report, hopefully someone will look into it.  I think the issue is that the "Password" field is only used for non-corporate WPA/WPA2, but with Corporate WPA/WPA2, it needs to use "UserPassword" and put in that sub-dictionary I mentioned.  Thanks!



This thread was automatically locked due to age.
Parents
  • Hi,

    We had the same issue, Our solution was to build a Network Device Enrollment Server and deploy a Client based certificate, this allows the device to continue connecting as long as the certificate is valid, even if the user changes their password.

    It also gets around our 90 day password reset policy causing mobile devices trying to connect with the old password and locking out the AD account.

    Regards,
    Bohdan

Reply
  • Hi,

    We had the same issue, Our solution was to build a Network Device Enrollment Server and deploy a Client based certificate, this allows the device to continue connecting as long as the certificate is valid, even if the user changes their password.

    It also gets around our 90 day password reset policy causing mobile devices trying to connect with the old password and locking out the AD account.

    Regards,
    Bohdan

Children
No Data