Editing SPNEGO (section)

{{Short description|Security protocol used with GSSAPI}}
{{Use dmy dates|date=November 2022}}
'''Simple and Protected GSSAPI Negotiation Mechanism''' ('''SPNEGO'''), often pronounced "spenay-go", is a [[GSSAPI]] "pseudo mechanism" used by client-server software to negotiate the choice of security technology. SPNEGO is used when a client application wants to authenticate to a remote server, but neither end is sure what authentication protocols the other supports. The pseudo-mechanism uses a protocol to determine what common GSSAPI mechanisms are available, selects one and then dispatches all further security operations to it. This can help organizations deploy new security mechanisms in a phased manner.

SPNEGO's most visible use is in [[Microsoft]]'s "HTTP Negotiate" [[authentication]] extension. It was first implemented in [[Internet Explorer]] 5.01 and IIS 5.0 and provided [[single sign-on]] capability later marketed as ''[[Integrated Windows Authentication]]''. The negotiable sub-mechanisms included [[NTLM]] and [[Kerberos (protocol)|Kerberos]], both used in [[Active Directory]]. The HTTP Negotiate extension was later implemented with similar support in:
* [[Mozilla]] 1.7 beta<ref>[https://bugzilla.mozilla.org/show_bug.cgi?id=17578 Mozilla bug 17578: I want Kerberos authentication and TGT forwarding]</ref>
* [[Mozilla Firefox]] 0.9
* [[Konqueror]] 3.3.1<ref>{{cite web | url=http://article.gmane.org/gmane.comp.kde.devel.kfm/6300 | title=Konqueror has SPNEGO support | work=Apache and Kerberos tutorial | access-date=30 May 2005 | url-status=live | archive-url=https://web.archive.org/web/20050419055107/http://article.gmane.org/gmane.comp.kde.devel.kfm/6300 | archive-date=19 April 2005 }}</ref>
* [[Google Chrome]] 6.0.472<ref>{{cite web | url=http://code.google.com/p/chromium/issues/detail?id=28282 | title=Support for SPNEGO authentication | work=Google Chrome Enhancement Request | access-date=20 November 2010 | url-status=live | archive-url=https://web.archive.org/web/20121111061907/http://code.google.com/p/chromium/issues/detail?id=28282 | archive-date=11 November 2012 }}</ref>