As a possible workaround (and I haven't tested this)... you could try setting a different User Agent string in Safari. I highly doubt this is an "Apple problem" -- this is most likely just a case of the SA device [naively] checking for specific environment strings. Again, this is just my conjecture. To test it... under Preferences in Safari, click Advanced and enable the check box for "Show Develop menu in menu bar" Then, when you visit the SA login page, click the Develop menu, then "User Agent", then choose a different User Agent string, such as Safari 5.0.6, Firefox, or even Internet Explorer. It's not ideal, but it might get your users by until a fix comes from Juniper.
... View more