Re: Authentication from the browser

2009-06-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alec, On 6/3/2009 12:25 PM, Alec Swan wrote: > Bill, thank you for your feedback. I read up on CLIENT-CERT and am now > surprised that Bill was the only one to mention it. It sounds like > CLIENT-CERT is the scheme that we should. We can generate cert

Re: Authentication from the browser

2009-06-03 Thread Alec Swan
Bill, thank you for your feedback. I read up on CLIENT-CERT and am now surprised that Bill was the only one to mention it. It sounds like CLIENT-CERT is the scheme that we should. We can generate certificates and ask our customer to distribute it to its users and have them install certificates in t

Re: Authentication from the browser

2009-06-03 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alec, On 6/2/2009 6:08 PM, Alec Swan wrote: >> ? You can't put HTTP headers "in" a link, unless you're processing >> it through some proxy mechanism... >> > > Looks like the last SecurityFilter build was released on Dec. 14, > 2004, which makes me

Re: Authentication from the browser

2009-06-03 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alec, On 6/2/2009 2:03 PM, Alec Swan wrote: > Hassan, I don't think that the goals are contradictory, because each goal > applies to its own group of users: our customer users and everybody else. > Customer users should not have to enter user name and

Re: Authentication from the browser

2009-06-02 Thread Bill Barker
"Alec Swan" wrote in message news:34abb48b0906021503t158542a5ube612b5ccfad0...@mail.gmail.com... > On Tue, Jun 2, 2009 at 2:34 PM, Jonathan Mast > wrote: > >> Alec, so basically members of your client company should be able to have >> direct access to a servlet that is otherwise restricted to a

RE: Authentication from the browser

2009-06-02 Thread Martin Gainty
ie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. >

Re: Authentication from the browser

2009-06-02 Thread Alec Swan
> > ? You can't put HTTP headers "in" a link, unless you're processing > it through some proxy mechanism... > Looks like the last SecurityFilter build was released on Dec. 14, 2004, which makes me hesitant to use it. I am wondering if it is possible to use JavaScript to include the user name and

Re: Authentication from the browser

2009-06-02 Thread Alec Swan
On Tue, Jun 2, 2009 at 2:34 PM, Jonathan Mast wrote: > Alec, so basically members of your client company should be able to have > direct access to a servlet that is otherwise restricted to a handful of > users who must authenicate themselves with a username/password login, > right? > Yes, this is

Re: Authentication from the browser

2009-06-02 Thread Hassan Schroeder
On Tue, Jun 2, 2009 at 1:01 PM, Alec Swan wrote: > We have one corporate customer who is putting a link to our servlet on their > intranet web page. Therefore, we know the domain name of the users who need > custom authentication. Seems iffy -- none of these users will ever be working remotely a

Re: Authentication from the browser

2009-06-02 Thread Jonathan Mast
Alec, so basically members of your client company should be able to have direct access to a servlet that is otherwise restricted to a handful of users who must authenicate themselves with a username/password login, right? One solution to this situation would be to create a simple servlet that snif

Re: Authentication from the browser

2009-06-02 Thread Alec Swan
I may not be explaining it clearly. We have one corporate customer who is putting a link to our servlet on their intranet web page. Therefore, we know the domain name of the users who need custom authentication. We can also tell the customer to put whatever we need in the link, such as HTTP header

Re: Authentication from the browser

2009-06-02 Thread Hassan Schroeder
On Tue, Jun 2, 2009 at 11:03 AM, Alec Swan wrote: > Hassan, I don't think that the goals are contradictory, because each goal > applies to its own group of users: our customer users and everybody else. > Customer users should not have to enter user name and password, but > everybody else should.

Re: Authentication from the browser

2009-06-02 Thread Alec Swan
Hassan, I don't think that the goals are contradictory, because each goal applies to its own group of users: our customer users and everybody else. Customer users should not have to enter user name and password, but everybody else should. Also, in general it is possible to authenticate a user with

Re: Authentication from the browser

2009-06-02 Thread Hassan Schroeder
On Tue, Jun 2, 2009 at 10:22 AM, Alec Swan wrote: > We would also like to continue using the existing authentication mechanism. > So, the question is how can we ... allow authentication to happen > without requiring the end-user to type in the user name and password? Your goals seem contradicto