Skip to main content
Question

MacOS DEP over Eduroam

  • September 5, 2017
  • 8 replies
  • 54 views
S
Forum|alt.badge.img+6

Hi Friends ,

We are now doing most provisioning using DEP and we have a JSS in the DMZ so clients can go through the process no matter where they are located . One problem we have is when the the user is going through the Welcome Wizard process on their MacBook , select the Eduroam network , it only asks for a password and not the username ... so cant proceed . I have confirmed with the network team that we have eduroam auth set to 802.1X authentication using TTLS . Is anyone successfully connecting to eduroam while going through the Apple Welcome wizard ?

Process works for iPad but have confirmed iOS WiFi requirements are a bit different for this to work .

    8 replies

    L
    Forum|alt.badge.img+16
    • Look
    • Valued Contributor
    • September 5, 2017

    iOS recently moved to allowing user:password authentication during Setup, previously you couldn't do that over Eduroam either, macOS still does not, I doubt DEP over Eduroam is going to be possible until that happens.

    S
    Forum|alt.badge.img+6
    • Slawford
    • Author
    • Contributor
    • September 5, 2017

    @Look 10.12 at least supports it , http://help.apple.com/deployment/macos/#/ior5e0df8ab7

    L
    Forum|alt.badge.img+16
    • Look
    • Valued Contributor
    • September 5, 2017

    @Slawford "The macOS Setup Assistant supports 802.1X authentication with username and password credentials using TTLS or PEAP."
    YAY!
    About time to, our entire Wi-Fi infrastructure is all user authenticated and it has been a real pain not being able to connect during Setup.
    I figured it was on the way given it appeared in iOS a couple of versions ago.

    D
    Forum|alt.badge.img+11
    • davidhiggs
    • Valued Contributor
    • September 10, 2017

    @Look It really went under the radar, I only came across it by chance when doing some testing on our dev wifi network.

    @Slawford We're using Cisco here. Ask your network team if you have both WPA1 and WPA2 PSK enabled (for legacy reasons). We found that when both are enabled for the SSID, it will cause the problem you're seeing. Either one can be enabled independently, just not together. If you have a dev network available for testing, ask them to duplicate your production SSID and remove WPA1. Let me know how you go!

    S
    Forum|alt.badge.img+6
    • Slawford
    • Author
    • Contributor
    • September 11, 2017

    @davidhiggs thanks champ , does look like that's how things are configured here , will make a change in dev and see how we go :)

    L
    Forum|alt.badge.img+16
    • Look
    • Valued Contributor
    • September 11, 2017

    Likewise, we still have WPA1 enabled, will test when I get another DEP device available.

    S
    Forum|alt.badge.img+6
    • Slawford
    • Author
    • Contributor
    • September 12, 2017

    Yep that did the trick! Thanks Mate :)

    D
    Forum|alt.badge.img+11
    • davidhiggs
    • Valued Contributor
    • September 12, 2017

    @Slawford Awesome to hear, no worries at all! Good luck @Look

    Terms & ConditionsCookie settingsAccessibility statement