I would like to clarify that MAC OSX 10.7 is not supported in IC 4.2R1 yet.
We only support Junos Pulse (only L3 authentication), Agentless (browser based) and native supplicant of MAC OSX.
Note: If this answers your question, you could mark this as accepted solution, that way it helps others as well.
Thanks for your patience.
OAC will be supported for 10.7 LION Mac OS only in our next major release 4.3 R1, this information is documented in
4.2 R1 release notes. OAC does not support Mac OS X 10.7 (Lion). (PR 658607, lookout for page#7
Currently 10.7 is supported with UAC and Junos Pulse Client ( you cane use this as a workaround if needed) and also for agent less access this is supported.
The informations are availbel in the below mentioned supported platform guide, you can access it using the below URL:
I am not aware of 4.3 R1 release date and availability, i recommend you to work with your local Juniper SE or account team to
know the 4.3R1 release date plan.
We are interested in this as well. What is the functional difference between OAC and Pulse on OS X 10.7?
I thought I read that Pulse on OS X could do native supplicant with SSO. Is that not the case?
Adding my problems into the mix.... We're using purely AD authentication, no certificates. I'm testing with a Lion install and the only option I have is to set the NIC up for "auto 802.1x" and that doens't seem to work. The Mac says it's authenticating, but the log in the UAC never show anything for that host.
I have sucessfully setup a Wyse ZeroClient terminal to use Username/Password authentication and that works with it's built in 802.1x supplicant...
When I look at the "Pulse" documentation, it says it doesn't work for IPSEC or 802.1x, so that appears useless...
We do not have a Web page for users to login, they either use a supplicant or they get bumped to the vendor network.
Are my Mac users SOL, or do I need to get the Apple Config Utility Server to create a specific 802.1x profile for them?
I think that MAC OS users are not the priority of Juniper. Features are always postponed to next release, next release, next release ! And when the features are in THE RELEASE, your hardware is too old...
Thanks for your update, I understand your concern.
We value your feedback however I would recommend you to work with your local Juniper Account Team who can involve you with Juniper Product management Team on this.