I have web applications that are behind https that only support spnego in an AD environment. We are able to use a series of AD servers to service the requests, from both the client and server side. We use basic authentication as a fail back in the event SPNEGO fails. This prompts the user for their username and password in the event the client does not have a valid TGT. We do this from Apache web servers, IIS servers. This works for Chrome, IE, FF, and other browsers. It works from Windows workstations, Linux workstations, Mac workstations.
The web server handles the handshake and passes the credentials onto the J2EE layer if the user successfully authenticates. If the user does not successfully authenticate, then they get a 401 error, which can be handled with an error page. What enterprise capabilities am I missing? http://modauthkerb.sourceforge.net/ Axton On Thu, Jun 30, 2011 at 2:30 PM, John Baker <[email protected]>wrote: > Axton > > To fully support SPNEGO, one requires both Kerberos+NTLMv2. To my > knowledge, there is no complete implementation outside of SSO Plugin, in and > out of the BMC market, let alone an implementation with AD failover support > and all the other features that serious clients demand from a product. > > > John > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
