- Jamf Nation Community
- Products
- Jamf Pro
- Safari 7.0 + Bluecoat Proxy - Internet Access issu...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Safari 7.0 + Bluecoat Proxy - Internet Access issues
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 12-16-2013 10:30 AM
Has anyone using a Bluecoat proxy experienced internet access issues after upgrading to mavericks? For the most part, Safari is basically unable to access internet sites - but Firefox and Chrome can access these sites using the same proxy.
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 12-16-2013 03:44 PM
How do you configure proxy on clients? Auto Discover? We use Blue coat and use auto discover (wpad) but I haven't tested safari in 10.9 much yet. Will take a look...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 12-16-2013 04:07 PM
In a quick test, it looks ok for me. Is it just really slow, or what makes it almost unusable?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 12-17-2013 08:02 PM
We do not have issues with our ProxySG and Mavericks. How is yours deployed? Inline, Transparent, Explicit? Are you doing client auth, if so is it from an exception page or Kerberos or what?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 12-29-2013 06:45 AM
I am having the same issues with our BlueCoat proxies and Mavericks. OCSPD is the issue because the proxy is sending back a request for credentials and the OS isn't respecting it and not providing the credentials or prompting the users to input them.. I opened a ticket with Apple Enterprise support and they acknowledged that it is an issue. We were able to duplicate it, but the only resolution was to create a system keychain that grabs the users proxy credentials if they are stored in the keychain.
Unfortunately, that doesn't work for us because we force a password change every 30 days so it would need to be running constantly along with the fact that not all of our users store the proxy credentials in the keychain.
An alternate way around this would be to allow the OCSPD user agent header unauthenticated access to the internet through the proxy. I am having the same issues with Safari and iTunes. Allowing the user agent header string works reliably and the ocspd process can only be initiated via the OS so the risk is reduced significantly.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 01-02-2014 07:33 AM
@jconte I was able to workaround the issue by turning off OCSP and CRL in Keychain > Preferences. Thinking back, we had to do the same thing in Lion to alleviate some proxy issues. I received the same feedback from Apple Support, that product management is aware of the issue and it will be addressed in an update - hopefully soon.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 01-07-2014 11:39 AM
Turning off OCSP and CRL in the keychain prefs seems to work with Safari, but I'm still getting proxy prompts for the App Store when trying to run updates. We just received word from enterprise support that they anticipate a fix in 10.9.2.
