> -----Original Message----- > From: Jens Bo Friis [mailto:[EMAIL PROTECTED] > Sent: Sunday, October 31, 2004 8:57 AM > To: Alan D. Cabrera > Cc: [EMAIL PROTECTED]; Bo Friis > Subject: Re[2]: adding support for pluggable authenticators (HTTP) (adding > support for SPNEGO/Kerberos) > > Hi Alan, > > > > >> -----Original Message----- > >> From: Bo Friis [mailto:[EMAIL PROTECTED] > >> Sent: Saturday, October 30, 2004 10:25 PM > >> To: [EMAIL PROTECTED] > >> Subject: adding support for pluggable authenticators (HTTP) (adding > >> support for SPNEGO/Kerberos) > >> > >> As I see it and correct me if im wrong, its not possible to plugin > >> custom authenticators and im not sure where to add this but I have > >> some suggestions. > >> > >> WebApplicationContext.initLoginConfig() instansiates the authenticator > >> based on the web app deployment descriptor. I would prefer to have the > >> ability to extend this list of authenticators, alternatively the > >> ability to replace one of the standard authenticators. > > A> What do you mean by extend the list of authenticators. It should be > A> possible add a SPNEGO support by writing your own Jetty Authenticator. > A> What problems are you encountering? > > It should be easy to implement the interface but how do I "activate" > my custom authenticator from the deployment descriptor? or is there > another way I just havnt found yet? > > The authenticator is instansiated by specifying on of the webapp > deployment descriptor keywords: BASIC, FORM, DIGEST, CLIENT-CERT. How > to I set my custom authenticator?
Actually, maybe writing a SPNEGOHandler would do the trick. Regards, Alan
