Re: External Auth

Herik,

        The URL is for a QUT specific. We have a messaging client here
at QUT the runs on PC's. We use this to tell users why they have failed
authentication. The message is usually something like so:

1) While trying to access "URL", your account went over quota.

2) Your username / password is incorrect.

3) The Authentication Server is currently unavailable.

etc.....

        So that is the reason behind passing the URL to the authenticator.
However, I would like to see the complete icpState being passed.

Anyway, seeya later,

-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
David Richards
Network Programmer
Internetworking Software Services, Computing Services
Queensland University of Technology
Level 12, 126 Margaret Street
Brisbane QLD 4001, Australia
E-mail: dj.richards@qut.edu.au
Ph: +61 7 3864 4347 Fax: +61 7 3864 5272
-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-

On Wed, 18 Nov 1998, Henrik Nordstrom wrote:

> David Richards wrote:
>
> > I am well aware that this is in squid. We are using this
> > technology here at QUT. However, the only problem we face
> > is that we had to hack the code so that not only were the
> > details of user and password were sent to the authenticator,
> > but also the client IP and URL they were trying to access.
>
> Client IP makes sense, but URL doesn't.
>
> The purpose of the authenticator is to validate who the user
> is, not if he has access to a given URL or not.
>
> See my other messages on this thread.
>
> ---
> Henrik Nordstrom
> Spare time Squid hacker
>
Received on Wed Nov 18 1998 - 15:40:50 MST