Mailinglist Archive: opensuse (4237 mails)
| < Previous | Next > |
RE: [SLE] yast update not working with Novell Border manager authentication?
- From: g.lams@xxxxxxxxxx
- Date: Mon, 2 Aug 2004 15:56:36 +0200
- Message-id: <OFF4D98366.C257BC26-ONC1256EE4.004BE027-C1256EE4.004C9508@xxxxxxxxxx>
In fact, it's what our novell administrator has done, i.e create an access
rule that allows the IP address of that machine to the site it needs to
reach. Then check the "autnehticate only when user attempts to access
restricted site" and put that rule on top of the others.
It works for our servers but several users, including myself, have
problems navigating a few sites including hotmail, yahoo
Gael
"Jesse Pretorius" <preycor@xxxxxxxxxxxxx> wrote on 02/08/2004 15.42.33:
> > Authentication has been implemented on our Novell BorderManager proxy
> > servers
> > I've setup the proxy in yast providing username and password but
before
> > being giving me the list of updates, there is the following error:
>
> BorderManager's login page is proprietary in a way that does not provide
an
> authentication request in a way that YaST expects it.
>
> AFAIK the only way around it would be to set the NBM to allow your
server's
> IP address to go through without requiring authentication.
>
>
rule that allows the IP address of that machine to the site it needs to
reach. Then check the "autnehticate only when user attempts to access
restricted site" and put that rule on top of the others.
It works for our servers but several users, including myself, have
problems navigating a few sites including hotmail, yahoo
Gael
"Jesse Pretorius" <preycor@xxxxxxxxxxxxx> wrote on 02/08/2004 15.42.33:
> > Authentication has been implemented on our Novell BorderManager proxy
> > servers
> > I've setup the proxy in yast providing username and password but
before
> > being giving me the list of updates, there is the following error:
>
> BorderManager's login page is proprietary in a way that does not provide
an
> authentication request in a way that YaST expects it.
>
> AFAIK the only way around it would be to set the NBM to allow your
server's
> IP address to go through without requiring authentication.
>
>
| < Previous | Next > |