"Heikki Linnakangas" <[EMAIL PROTECTED]> writes: > Magnus Hagander wrote: > >> The wire protocol is the same for them. It's a matter of which *client >> library* should be used to produce the packets that go over the network. >... > On Windows, why would you need GSSAPI, if SSPI comes with the operation > system? What's the difference between the libraries? Can you try SSPI > first, and fall back to GSSAPI?
Am I right in thinking that while the client<->postgres protocol may be the same the actual authentication tokens are different? That is, if you have a Windows Active Directory server then using SSPI will use your Windows credentials obtained from that server to log you in whereas if you used the MIT GSSAPI library it would try to use your Kerberos tickets for which it would look elsewhere? What confuses me here is that I don't understand how this relates to applications. You keep talking about using the connection string which may be appropriate for a user-oriented application like psql. But in the general case surely the application needs to be able to control the authentication process and be able to provide credentials of its choice? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
