Skip site navigation (1) Skip section navigation (2)

Re: PsqlODBC with a SSL connection

From: Terry Lorber <tlorber(at)atlantiscomp(dot)com>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Re: PsqlODBC with a SSL connection
Date: 2007-01-05 22:25:03
Message-ID: 459ED03F.20904@atlantiscomp.com (view raw or flat)
Thread:
Lists: pgsql-odbc
Looks like I need to include Ssslmode=require in the connection string 
(just Ssl=true) doesn't do it.  Here's a nice list of attributes from 
the Npgsql, 
http://npgsql.projects.postgresql.org/docs/manual/UserManual.htm, website:

<pre>
 Gets or sets the string used to connect to a PostgreSQL database.

        /// Valid values are:
        /// Server:                     Address/Name of Postgresql Server;
        /// Port:                       Port to connect to;
        /// Protocol:                   Protocol version to use, instead of automatic; Integer 2 or 3;
        /// Database:                   Database name. Defaults to user name if not specified;
        /// User Id:                    User name;
        /// Password:                   Password for clear text authentication;
        /// SSL:                        True or False. Controls whether to attempt a secure connection. Default = False;
        /// Pooling:                    True or False. Controls whether connection pooling is used. Default = True;
        /// MinPoolSize:                Min size of connection pool. Default: 1;
        /// MaxPoolSize:                Max size of connection pool. Default: 20;
        /// Encoding:                   Encoding to be used; Can be ASCII or UNICODE. Default is ASCII. Use UNICODE if you are having problems with accents.
        /// Timeout:                    Time to wait for connection open in seconds. Default is 15.
        /// CommandTimeout:             Time to wait for command to finish execution before throw an exception. In seconds. Default is 20.
        /// Sslmode:                    Mode for ssl connection control. 
        /// ConnectionLifeTime:         Time to wait before closing unused connections in the pool in seconds. Default is 15.
        /// SyncNotification:           Specifies if Npgsql should use synchronous notifications
        Encoding can be ASCII or UNICODE. If your application uses characters with accents and with default settings it doesn't work, try changing that.
        Min pool size when specified will make NpgsqlConnection pre allocates this number of connections with the server.
        Sslmode can be one of the following values: 
            Prefer - If it is possible to connect using ssl, it will be used.
            Require - If an ssl connection cannot be made, an exception is thrown.
            Allow - Not supported yet, just connects without ssl.
            Disable - No ssl connection is done.
            Default is Disable.
</pre>        


I can't say these are all valid for pgsqlODBC, but it's a start.  Shouldn't this be somewhere on the postgresql.org site?  If I've missed it, please show me the light!

tgl


Terry Lorber wrote:
> I'm having difficulty connecting in SSL mode with the "PostgreSQL 
> ANSI" driver from a Win32 machine to a PostgreSQL 8.2 installation on 
> a GNU/Linux machine.
>
> I can connect from my client w/ SSL using "psql" from the command line 
> fine, also connecting using plain ODBC works too.  When I try to force 
> the SSL connection (by making changes to the servers pg_hba.conf 
> file), I'm told SSL is off.
>
> Is there something in the connection string I use to tell the driver 
> to use SSL?
>
> Thanks.
>
> tgl
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
>


In response to

Responses

pgsql-odbc by date

Next:From: noreplyDate: 2007-01-08 07:07:29
Subject: [ psqlodbc-Bugs-1000968 ] Unicode driver does not work with multibyte database name
Previous:From: Terry LorberDate: 2007-01-05 19:29:59
Subject: PsqlODBC with a SSL connection

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group