#8007: Greenplum - create user GUI - try to use that user as login for ADStudio server registration - org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host

swissarmyknife(*) reported 2012-12-04T21:54:22Z · funfun last modified 2012-12-04T22:37:28Z

Greenplum - create user GUI - try to use that user as login for ADStudio server registration - org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host

doc

Dev	funfun
QA	SachinPrakash

Priority	Low
Complexity	Unknown

Component	App - Visual Editing
Version	13.0

Sachin asked me to report this one.

Version: 13.0-dev-41

Build #: 30427

Build Date: 2012-Dec-04 10:21:38 AM

Operating Environment: Windows XP (5.2, amd64) / Cp1252 / en / US / Sun Microsystems Inc. 1.6.0_35-b10

Memory: Max=891,092,992; Total=436,862,976; Free=340,016,080; CPUs=8

1. create a user called something like jonzzz ( I used jonppp as you can see below ). See attached for what should be checked in the General and Database Access tabs of the CREATE user GUI.

Here's a "Script Object to Window As..." for the user so you can see its permissions

CREATE USER jonppp WITH SYSID 268541 PASSWORD '<password>'

NOCREATEDB

NOCREATEUSER

GRANT CONNECT, TEMP ON DATABASE jonqatest TO jonppp

GRANT CREATE, USAGE ON SCHEMA public TO jonppp

ALTER GROUP jonathantestgroup ADD USER jonppp

2. During the creation, the Messages tab of the CREATE User dialog will give this message

resource queue required -- using default resource queue "pg_default"

3. Once you see the user in the Security node of the schema browser, create a server registration to Greenplum with this user's credentials.

4. When you click ok in the Greenplum server registration dialog to complete the creation of the server connection for ADStudio, you receive the following

org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "10.168.1.93", user "jonppp", database "jonqatest", SSL off

at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)

at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:106)

at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:64)

at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:123)

at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:28)

at org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:20)

at org.postgresql.jdbc4.AbstractJdbc4Connection.<init>(AbstractJdbc4Connection.java:30)

at org.postgresql.jdbc4.Jdbc4Connection.<init>(Jdbc4Connection.java:22)

at org.postgresql.Driver.makeConnection(Driver.java:391)

at org.postgresql.Driver.connect(Driver.java:265)

at java.sql.DriverManager.getConnection(DriverManager.java:582)

at java.sql.DriverManager.getConnection(DriverManager.java:154)

at \\...\\ .\\हिñçêČάй語简�?한\\.Sꌎꒄꍥꈫ private.yV(Unknown Source)

at \\...\\ .\\हिñçêČάй語简�?한\\.Sꌎꒄꍥꈫ private.Z(Unknown Source)

at \\...\\ .\\हिñçêČάй語简�?한\\.Sꌎꒄꍥꈫ private.getConnection(Unknown Source)

at \\...\\ .\\हिñçêČάй語简�?한\\.Kꑺ⠁ꋬꃩ 7 Object.process(Unknown Source)

at com.common.ui.util.BackgroundThread.run(Unknown Source)

5 attachments

yser gui - database access tab

2012-12-04T21:54:22Z

41 KB
user gui - general tab

2012-12-04T21:54:22Z

32 KB
Greenplum pg hba conf error

2012-12-04T21:54:22Z

148 KB
Greenplum pg hba conf error 2

2012-12-04T21:54:23Z

209 KB
jonppp_jonathantestgroupmember.png

2012-12-04T21:54:23Z

44 KB

All Comments (3) Change History

swissarmyknife(*) 2012-12-04T22:00:08Z

The only user I've ever been able to connect to Greenplum with via a server registration is the user

dba

Whereas, I can create users in Postgresql via the create user gui, then use that user within a server registration inside Aqua Data Studio to connect.

swissarmyknife(*) 2012-12-04T22:28:09Z

page 36 of the Greenplum Admin Guide

"In Greenplum Database, the pg_hba.conf file of the master instance controls client access and authentication to your Greenplum system. The segments also have pg_hba.conf files, but these are already correctly configured to only allow client connections from the master host. The segments never accept outside client connections, so there is no need to alter the pg_hba.conf file on your segments.

The general format of the pg_hba.conf file is a set of records, one per line. Blank lines are ignored, as is any text after the # comment character. A record is made up of a number of fields which are separated by spaces and/or tabs. Fields can contain white space if the field value is quoted. Records cannot be continued across lines. Each remote client access record is in the format of:

host database role CIDR-address authentication-method

Each UNIX-domain socket access record is in the format of:

local database role authentication-method

A DBA would have to modify a config file in order to allow access for additional user... it's not a problem with the CREATE User GUI..., this is how Greenplum works.

funfun 2012-12-04T22:37:28Z

I was trying to reply and asking you to take a look Chapter 6: Configuring Client Authentication of Administrator Guide, but you found out answer yourself. I noticed this problem while working on the implementation of the User Dialog, but I don't have access to the machine where Greenplum Server is hosted, hence, I could not provide more further information.

Search Tips

Aqua Data Studio / nhilam

Greenplum - create user GUI - try to use that user as login for ADStudio server registration - org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host

5 attachments

Issue #8007

Completion

Search Tips

Aqua Data Studio / nhilam

Title

Greenplum - create user GUI - try to use that user as login for ADStudio server registration - org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host

5 attachments

Issue #8007

Completion