Re: [NOVICE] Can"t get MS Access via ODBC (or MapServer) to "see" the data unless the user is a "sup

Regina,

Perfect - that was it... fixed it up for both MapServer and ODBC...

With hindsight, this seems logical of course - but wasn't not made clear in=
the reference text I am using, at least to me ("PostgreSQL 8 for Windows")=
) - part of the whole newbie thing I guess... :-)

(Confirmed that I was logging in as FRED (sic) to phpPgAdmin without inheri=
tance, just tested... hmmm... more to learn!)

(aside - the three *group* roles I set up for my main 'production' database=
have somehow 'migrated' to *login* roles when I look at them after restati=
ng the Widows service and reopening pgAdmin - but still seem to be working =
as group roles (I think...) - pgAdmin v1.8.0 revision dated 10/19/07 and Po=
stgreSQL )

=20
Cheers:
GREG COCKS
gcocks |at| stoller.com
=20
=20
=20
--------------------------------
=20
-----Original Message-----
From: Obe, Regina [mailto:robe.dnd@cityofboston.gov]=20
Sent: Monday, December 03, 2007 5:23 AM
To: Greg Cocks; PostgreSQL List - Novice
Subject: RE: [NOVICE] Can't get MS Access via ODBC (or MapServer) to 'see' =
the data unless the user is a 'super user'...


Its strange that it works in PhpPgAdmin unless you aren't really logging i=
n as Fred as you think you are.

Assuming your privledges are set correctly on your group, I would suspect t=
hat maybe you don't have Fred set to inherit rights from parent roles.

That threw me for a loop the first time I saw it that you can have a role t=
hat is not set to inherit rights from its parent roles. So in order for it=
to use the rights of its parent, it has to do a set role or be set to inhe=
rit.

So to make sure a login is set to inherit rights from its parent role, make=
sure you have something like

CREATE ROLE fred LOGIN
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
GRANT mapservgroup TO fred;

Hope that helps,
Regina

-----Original Message-----
From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice-owner@postgres=
ql.org] On Behalf Of Greg Cocks
Sent: Friday, November 30, 2007 2:58 PM
To: PostgreSQL List - Novice
Subject: [NOVICE] Can't get MS Access via ODBC (or MapServer) to 'see' the =
data unless the user is a 'super user'...

Hello,

Yep, a newbie, at least to PostgreSQL + ODBC / MapServer... :-)

I have:

- built and populated a PostgreSQL database (including PostGIS, in case th=
at matters in this case)

- set up ODBC (using psqlodbc-08_02_0500), using the Unicode version as a =
System DNS

- successfully connected to the tables in PostgreSQL from an Access 'front=
end' I built, updated tables, etc, etc


The user in PostgreSQL/ODBC was a super user - lets call that user FRED...


Wanting now to 'lock this down' a bit security-wise, I:

- set FRED as *not* being a Super User

- made a new group role, lets call that grpWrite

- assigned (sic) FRED to grpWrite

- set the GRANT permissions on all the non-system tables to be SELECT, INS=
ERT, DELETE and UPDATE (took me a bit to find and use that function!), so t=
he grpWrite privileges on each non-system table reads 'arwdx'=20

- *tested FRED with phpPgAdmin - works just as expected*, full read write =
access to the data - but NOT things such as vacuum, etc

- checked the TEST on my ODBC driver, 'CONNECTION SUCCESSFUL'

When I go to the Access 'front end' now, I can refresh all the tables in th=
e Linked Table Manager (suggest the CONNECT is A-OK) but when I try and vie=
w data in a table, etc I get the error in MS Access:

ODBC--call failed
ERROR: permission denied for relation ;
Error while executing the query (#7)

Tried, with no luck:

- setting the GRANT on the group role to include REFERENCES

- opening the MS Access database on the PostgreSQL server

- as a last resort, setting the GRANT in grpWrite to ALL

The minute I change FRED back to being a Super User, works like a charm...

** Suggestions and experiences gratefully accepted! **

Note that MapServer has the same need for FRED (sic) to be a Super User...

Thanks in advance!



----------
Regards,
GREG COCKS
GIS Analyst V
Gcocks |at| stoller.com
S. M. Stoller Corp
105 Technology Drive, Suite 190
Broomfield, CO 80021
www.stoller.com
303-546-4300
303-443-1408 fax
303-546-4422 direct
303-828-7576=A0cell


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Re: [NOVICE] Can"t get MS Access via ODBC (or MapServer) to "see" the data unless the user is a "sup

This is a multi-part message in MIME format.

------_=_NextPart_001_01C835D5.103BF396
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm not quite sure about how the switching from Group Role to Login =
Role happened. =20
=20
Actually there really isn't a difference between Login Role and Group =
Roles. They are both Roles. Login Role is really a subclass of Group =
Role or just rather role so to speak
=20
A login role is simply a Group role with the attribute Login checked. =
PgAdmin just groups them differently mostly for historical reasons I =
think and because people are used to thinking in terms of Groups and =
Logins. =20
=20
Maybe somehow the Login checkbox got checked. If you pull them up in =
PgAdmin III do you see the Login checkbox checked on them?
=20
Hope that helps,
Regina

________________________________

From: Greg Cocks [mailto:gcocks@stoller.com]
Sent: Mon 12/3/2007 12:42 PM
To: Obe, Regina
Cc: PostgreSQL List - Novice; pgsql-odbc@postgresql.org
Subject: RE: [NOVICE] Can't get MS Access via ODBC (or MapServer) to =
'see' the data unless the user is a 'super user'...



Regina,

Perfect - that was it... fixed it up for both MapServer and ODBC...

With hindsight, this seems logical of course - but wasn't not made clear =
in the reference text I am using, at least to me ("PostgreSQL 8 for =
Windows")) - part of the whole newbie thing I guess... :-)

(Confirmed that I was logging in as FRED (sic) to phpPgAdmin without =
inheritance, just tested... hmmm... more to learn!)

(aside - the three *group* roles I set up for my main 'production' =
database have somehow 'migrated' to *login* roles when I look at them =
after restating the Widows service and reopening pgAdmin - but still =
seem to be working as group roles (I think...) - pgAdmin v1.8.0 revision =
dated 10/19/07 and PostgreSQL )


Cheers:
GREG COCKS
gcocks |at| stoller.com



--------------------------------

-----Original Message-----
From: Obe, Regina [mailto:robe.dnd@cityofboston.gov]
Sent: Monday, December 03, 2007 5:23 AM
To: Greg Cocks; PostgreSQL List - Novice
Subject: RE: [NOVICE] Can't get MS Access via ODBC (or MapServer) to =
'see' the data unless the user is a 'super user'...


Its strange that it works in PhpPgAdmin unless you aren't really =
logging in as Fred as you think you are.

Assuming your privledges are set correctly on your group, I would =
suspect that maybe you don't have Fred set to inherit rights from parent =
roles.

That threw me for a loop the first time I saw it that you can have a =
role that is not set to inherit rights from its parent roles. So in =
order for it to use the rights of its parent, it has to do a set role or =
be set to inherit.

So to make sure a login is set to inherit rights from its parent role, =
make sure you have something like

CREATE ROLE fred LOGIN
NOSUPERUSER INHERIT NOCREATEDB NOCREATEROLE;
GRANT mapservgroup TO fred;

Hope that helps,
Regina

-----Original Message-----
From: pgsql-novice-owner@postgresql.org =
[mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Greg Cocks
Sent: Friday, November 30, 2007 2:58 PM
To: PostgreSQL List - Novice
Subject: [NOVICE] Can't get MS Access via ODBC (or MapServer) to 'see' =
the data unless the user is a 'super user'...

Hello,

Yep, a newbie, at least to PostgreSQL + ODBC / MapServer... :-)

I have:

- built and populated a PostgreSQL database (including PostGIS, in case =
that matters in this case)

- set up ODBC (using psqlodbc-08_02_0500), using the Unicode version as =
a System DNS

- successfully connected to the tables in PostgreSQL from an Access =
'front end' I built, updated tables, etc, etc


The user in PostgreSQL/ODBC was a super user - lets call that user =
FRED...


Wanting now to 'lock this down' a bit security-wise, I:

- set FRED as *not* being a Super User

- made a new group role, lets call that grpWrite

- assigned (sic) FRED to grpWrite

- set the GRANT permissions on all the non-system tables to be SELECT, =
INSERT, DELETE and UPDATE (took me a bit to find and use that =
function!), so the grpWrite privileges on each non-system table reads =
'arwdx'

- *tested FRED with phpPgAdmin - works just as expected*, full read =
write access to the data - but NOT things such as vacuum, etc

- checked the TEST on my ODBC driver, 'CONNECTION SUCCESSFUL'

When I go to the Access 'front end' now, I can refresh all the tables in =
the Linked Table Manager (suggest the CONNECT is A-OK) but when I try =
and view data in a table, etc I get the error in MS Access:

ODBC--call failed
ERROR: permission denied for relation ;
Error while executing the query (#7)

Tried, with no luck:

- setting the GRANT on the group role to include REFERENCES

- opening the MS Access database on the PostgreSQL server

- as a last resort, setting the GRANT in grpWrite to ALL

The minute I change FRED back to being a Super User, works like a =
charm...

** Suggestions and experiences gratefully accepted! **

Note that MapServer has the same need for FRED (sic) to be a Super =
User...

Thanks in advance!



----------
Regards,
GREG COCKS
GIS Analyst V
Gcocks |at| stoller.com
S. M. Stoller Corp
105 Technology Drive, Suite 190
Broomfield, CO 80021
www.stoller.com
303-546-4300
303-443-1408 fax
303-546-4422 direct
303-828-7576 cell


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.




------_=_NextPart_001_01C835D5.103BF396
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=0A=
=0A=
=0A=
=0A=