When accessing a UAG server from a Macintosh computer, you might run into this error:
“Client compliance for site access cannot be verified. There is a problem verifying the identity of the site. This might affect your site experience, depending on corporate access policy.”
On a Macintosh computer, UAG uses a special version of the client components, written in Java (as opposed to the regular client components, which are Active-X components). To troubleshoot this, you need to open the Java console, and see what it says. To do so:
1. Open the Java Preferences utility, normally located in /Applications/Utilities/Java/J2SE 5.0
2. Enable tracing, logging, and Show console:
Within the console, type the command -verbose to make sure the console logs anything with a high level of detail. The extra verbose log should be able to shed some light on what’s going on. For example, in a recent case, the log was showing this:
Wed Oct 03 11:09:54 2012 Installing file /Users/crawbil/Forefront UAG Remote Access Agent/securesharechrobinsoncom/secureshareportal1/agent_mac_helper_64.jar Wed Oct 03 11:09:55 2012 5145 bytes copied ... Wed Oct 03 11:09:55 2012 Verifying agent signature. Wed Oct 03 11:09:55 2012 Fatal error: signature does not exist!
Although this would lead to a generic error (like in the screenshot above), the text in the log actually shows exactly what’s up, and the file name shown, agent_mac_helper_64.jar, is the cause of the problem. The problem here stems from the fact that UAG does not have a 64 bit version of the Java client components for Mac (or Linux, for that matter). Modern Macs do run 64 bit by default, so for those, the only thing one can do is configure the browser to run in 32 bit. To do, follow these steps:
Similar actions can be taken on other applications, like FireFox.
Thanks, tried this yesterday, but Java 7 on Mac is 64 bit only, couldn't find Java 6 for Mac, any idea?
This is why we are getting rid of UAG, we cant get the new OSX to connect as the Java components are 32bit only.