* Christian Ullrich (chris@xxxxxxxxxxxxxx) wrote: > I tried to fix it using the reverse of they one-line fix that worked > in both JDBC and libpq. There, the problem was that they only > supported GSSAPI and had no clue about SSPI (except libpq on > Windows). The fix was to basically declare GSSAPI and SSPI to be the > same. It didn't work. If Npgsql does the same as libpq-on-Windows, it should all work just fine.. > In Npgsql's case, the problem is the other way around -- it only > knows SSPI. While making GSSAPI the same as SSPI should work in > principle, there must be some difference somewhere. Well, what happened after you hacked Npgsql? It's possible there's a bug or something it's doing different from libpq-on-Windows that is causing a problem, or it might simply be an issue with configuration (for example, you have to use POSTGRES as your server-side princ because Windows is case-insensitive). Thanks, Stephen
Attachment:
signature.asc
Description: Digital signature
