Bordermanager 3.8 SSL Proxy & Macintosh/Safari Browser

Question

Does anyone know if the Safari browser now included with the Mac OS X
10 is
compatible with BM 3.8 SSL Proxy? The SSL Proxy we have set up works
with
all other PCs, but I can't get it to work with the Safari and I can't
get an
answer from either Novell or Apple as to whether this is even a
supported
configuration. All I get is a reference to the login page with an
error
that a secure connection cannot be made. I have a school client who
was
just given 180 of these IMAC notebooks by the State and I need to get
them
working through their Bordermanager. I see there are definitely some
issues
with IE and Macs with SSL Proxy. Is there another browser, such as
Netscape, where this might work better.
What about using a third party novell client for Macs (like from
proform).
Would that be able to use clntrust authentication instead or is it not
a
true client32? Thanks!!

Answer 1

Hi Craig,
you've misunderstood what I meant (I guess I should have worded it
better).
What I meant was:
1. If you've already logged in (using another browser) Safari seems to
work
OK (but not necessarily for SSL)
2. that (it looks like) the reason Safari can't be used to login is
because
it's not using the proxy for the SSL login page requests - and to
login to
BM you must use the proxy to make the login request.
Safari error:
Could not open the page.
Could not open the page
https://proxy:444/BM-Login/?%22http:...novell.com/%22 because
Safari
could not establish a secure connection to the server "proxy".
Again, from this (and more) Safari is trying to Connect directly to
https://proxy:444 - instead of requesting the entire URL from the BM
proxy
(proxy:8080).
The same sort of problem can be created in other browsers by
configuring
them to not use a proxy for HTTPS/SSL requests.
-Sandy
"Craig Johnson" <[email protected]> wrote in message
news:[email protected]..
> In article <HLaLb.8715$[email protected]>, Sandy
wrote:
> > Once authenticated (using IE or Mozilla), Safari works through the
proxy.
> > (It looks like Safari is bypassing the proxy for SSL requests.)
> >
> Once a host is authenticated, a browser doesn't 'bypass' the ssl
login, it
> is already authenticated. Once authenticated, the proxy holds the
> authentication association between the requesting IP and the user
ID.
> Until the idle timeout expires, another authentication request is
not sent
> to the browser from the proxy.
>
> Craig Johnson
> Novell Support Connection SysOp
> *** For a current patch list, tips, handy files and books on
> BorderManager, go to http://www.craigjconsulting.com ***
>