I am not sure; I think it is Apple; but it could be something Juniper needs to change.
There is another thread specifically for this and will be updated as I find out more.
We opened a case with JTAc and they are working ona possible work around, but you may need to update to the latest OS version 7.1 R4 set to be released in August.
If anyone has a work around in the mean time, please post it ASAP. I have a ton of users who now cannot get into our Citrix environment as a result of the update.
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.
Hi, I have the same problem with my citrix ICA - I thought of the user agent string - however this didnt fool it, I still get the same error message
That was with lion using uagent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.0 Safari/534.48.3_
@[email protected] wrote:That was with lion using uagent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.0 Safari/534.48.3_
That's the default Safari 5.0 user-agent string, I believe. You could try something older and more widely compatible like Firefox 4. It may also be looking for the OS string, where it says "Intel Mac OS X 10_7," you can manually remove that part from the UA string or set it to an older version of OS X by setting "Other" in the Safari -> Develop -> User Agent menu and see if that works.
Here is my workaround to get JSAM working on Lion.
1) Download and install Pacifist from: http://www.charlessoft.com/Pacifist.dmg
2) Download and Mount JavaForMacOSX10.6Update5 from http://support.apple.com/kb/DL1360
3) Download and Mount JavaForMacOSX10.7 from http://support.apple.com/kb/DL1421
4) Launch Pacifist and select Open Package
5) Select the mounted JavaForMacOSX10.6Update5.pkg
6) Hit install, when it prompts always select "Replace"
7) After it is complete, select Open Package and select the JavaForMacOSX10.7.pkg
8) When it prompts select "Replace"
9) You can copy Safari 5.0.5 from SL or if you do not have access to a SL machine
10) Download and mount Safari 5.0.5 from
http://appldnld.apple.com.edgesuite.net/content.info.apple.com/Safari5/041-0564.20110413.Fi9pb/Safar...
11) In Pacifist select Open Package and select the Safari 5.0.5 pkg file
12) This time select Extract and place it onto your desktop
13) Go to the Safari5.0.5SnowLeopard folder on your desktop, inside of that you will see an Applications folder, open that and you will see Safari, you can rename this Safari, I named mine Safari 5.0.5 and copy it to your main Applications folder or whereever you want.
14) Launch this Safari and go to About and make sure it says 5.0.5
15) Try it out.
Confimred this procedure currently works with Lion for JSAM. It's relatively safe as well (should be)
Note when installing the avaForMacOSX10.6Update5_ I encountered on both lion machines I tested on a few (maybe a dozen in a row? ) errors about folders not being able to replace files - just keep on going, this won't be a problem.
For SL users who just upgraded safari,you just need a copy of safari 505 and use that - the cocoa java bindigns needed are installed there.
There must be a simpler solution though....
I did the following to login successfully. Network Connect loaded fine.
1. Reset Safari. Safari menu -> Reset Safari_
2. Open Java Preference (Applications - Utilities) and check 'Enable apple plug-in and Web Start Applications._
I hope this is helpful...
This is additionally ironic as we have a case open for Network Connect for Mac where Juniper claimed OS X Lion would fix it. If "fix" means "it's not supported, so it's not broken anymore" I suppose they did.