Re: Does psycopg2 support Kerberos for Postgres? - Mailing list psycopg
From | Yang Gao |
---|---|
Subject | Re: Does psycopg2 support Kerberos for Postgres? |
Date | |
Msg-id | 12ba3642df6c4d689005ecf20c90a51b@exmbdft5.ad.twosigma.com Whole thread Raw |
In response to | Re: Does psycopg2 support Kerberos for Postgres? (Adrian Klaver <adrian.klaver@aklaver.com>) |
Responses |
Re: Does psycopg2 support Kerberos for Postgres?
|
List | psycopg |
Got it, so psycopq uses the Postgres c-lib directly. Then, what is the recommended way of managing libpq? Looks like whenI installed psycopq from PyPi, it also pulled down this dependency which has no Kerberos support. Is there better wayto overwrite this dependency rather than manually swap it out? Thanks. Yang -----Original Message----- From: Adrian Klaver [mailto:adrian.klaver@aklaver.com] Sent: Tuesday, December 06, 2016 12:15 PM To: Yang Gao; 'psycopg@postgresql.org' Subject: Re: [psycopg] Does psycopg2 support Kerberos for Postgres? On 12/06/2016 08:28 AM, Yang Gao wrote: > That's a very good question. I pulled out the 2 libqp libraries. One in the default python installation that my psycopg2uses and the other used in my pyodbc experiment where Kerberos works. > They are of the same name, but different builds. Looks like I was using a lib without Kerberos support! > > If I replace the lib with the Kerberos supporting one, everything starts to work. > > Thank you very much! > > A further question, does psycopg2 respect the unixODBC's odbcinst.ini and odbc.ini (didn't find it in documentation)? Isthere way to explicitly specify the driver library? psycopg2 knows nothing about ODBC, so it will not look at those files. In other words psycopg2 != psqlodbc. > > Yang > > yangg@home:/proc/24196$ ldd > /home/yangg/.conda/envs/py2/lib/libpq.so.5.8 > shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory > linux-vdso.so.1 => (0x00007ffd38db5000) > libssl.so.1.0.0 => /home/yangg/.conda/envs/py2/lib/./libssl.so.1.0.0 (0x00007fcecf7e7000) > libcrypto.so.1.0.0 => /home/yangg/.conda/envs/py2/lib/./libcrypto.so.1.0.0 (0x00007fcecf3b0000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fcecf178000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fcecedeb000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fcecebe7000) > /lib64/ld-linux-x86-64.so.2 (0x0000559f3b33b000) > yangg@home:/proc/24196$ ldd > /home/yangg/vats_code/.base_universe/current-architecture/ext/public/p > sqlodbc/09/05/0100/dist/lib/libpq.so.5.8 > shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory > linux-vdso.so.1 => (0x00007ffee39e1000) > libssl-opt.so.1.0.0 => /opt/openssl/1.0/lib/libssl-opt.so.1.0.0 (0x00007f0b7e1e9000) > libcrypto-opt.so.1.0.0 => /opt/openssl/1.0/lib/libcrypto-opt.so.1.0.0 (0x00007f0b7dda7000) > libgssapi_krb5.so.2 => /opt/mitkrb5/lib/libgssapi_krb5.so.2 (0x00007f0b7db61000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0b7d92a000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0b7d59d000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0b7d398000) > libkrb5.so.3 => /opt/mitkrb5/lib/libkrb5.so.3 (0x00007f0b7d0d6000) > libk5crypto.so.3 => /opt/mitkrb5/lib/libk5crypto.so.3 (0x00007f0b7cea7000) > libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f0b7cca2000) > libkrb5support.so.0 => /opt/mitkrb5/lib/libkrb5support.so.0 (0x00007f0b7ca97000) > libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f0b7c881000) > /lib64/ld-linux-x86-64.so.2 (0x000055ec0f899000) > -- Adrian Klaver adrian.klaver@aklaver.com