Talk:Generic Security Services Application Programming Interface: Difference between revisions

Revision as of 04:42, 1 October 2006

Revision as of 21:28, 16 October 2007

Line 11:

*SSPI [http://msdn.microsoft.com/library/en-us/secauthn/security/authentication_functions.asp] (wire-compat only),

*SAP [ftp://ftp.sap.com/pub/ietf-work/gssapi/gsskrb5/],

**SAP is not a GSS-API implementation; it simply uses GSS-API [[User:SamHartman|SamHartman]] 21:28, 16 October 2007 (UTC)

but who else?

- [[User:Dleonard|DLeonard]] 04:42, 1 October 2006 (UTC)

Line 43 ⟶ 44:

how many do you recognize?

==Problems With the Article==

I read the article and noticed several problems that I don't have time to work on now so I decided to document them.

* I don't understand how [[RADIUS]]is a competing technology

* I think the proper abbreviation is GSS-API not GSSAPI; see RFC 2743.

* I'm not convinced that impersonationa is incompatible with IETF GSS-API. in particular GSS-API does provide a credential delegation mechanism. The only interisting thing behind impersonation is that you are able to tell the local OS to use the credential for everything including local access checks. For every GSS-API operation you can use the delegated credential just as in Windows. However you need a specific OS call to use that for local operations and that is in fact outside the scope of GSS-API.