Hi Vishal Ya you are right and the order is same and the command is like that only.
I am opening it through pgAdmin only.. Thanks & Regards, Shashwat Nigam<mailto:[EMAIL PROTECTED]> | Software Engineer | Geographical Information System Satyam Computer Services Limited<http://www.satyam.com/>, Hyderabad | MOBILE: +919951467324 | From: Vishal Arora [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 2:47 PM To: Shashwat_Nigam; [EMAIL PROTECTED] Subject: RE: [ADMIN] Regarding access to a user Hi Shashwat, I presume your user is hmri and the database is hmri_database, is it correct? if yes - your pg_hba.conf entry should be as following (if you are connecting to postgres on the same machine) host hmri_database hmri 127.0.0.1/32 md5 Can you tell me what command are you using to connect to the server and what environment is it? Regards Vishal ________________________________ From: [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] CC: pgsql-general@postgresql.org; [EMAIL PROTECTED]; [EMAIL PROTECTED] Date: Thu, 21 Aug 2008 14:35:43 +0530 Subject: Re: [ADMIN] Regarding access to a user Dear Vishal Thanks for the help but by doing this an error is generated at the time when the user is trying to log in with the following message: " Access to database denied The server doesn't grant access to the database: the server reports FATAL: no pg_hba.conf entry for host "127.0.0.1", user "hmri", database "postgres", SSL off To access a database on a PostgreSQL server, you first have to grant primary access to the server for your client (Host Based Authentication). PostgreSQL will check the pg_hba.conf file if a pattern that matches your client address / username / database is present and enabled before any SQL GRANT access control lists are evaluated. The initial settings in pg_hba.conf are quite restrictive, in order to avoid unwanted security holes caused by unreviewed but mandatory system settings. You'll probably want to add something like host all all 192.168.0.0/24 md5 This example grants MD5 encrypted password access to all databases to all users on the private network 192.168.0.0/24. You can use the pg_hba.conf editor that is built into pgAdmin III to edit the pg_hba.conf configuration file. After changing pg_hba.conf, you need to trigger a server configuration reload using pg_ctl or by stopping and restarting the server process. " Please provide futher proceedings Thanks & Regards, Shashwat Nigam<mailto:[EMAIL PROTECTED]> | Software Engineer | Geographical Information System Satyam Computer Services Limited<http://www.satyam.com/>, Hyderabad | MOBILE: +919951467324 | From: Vishal Arora [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 2:29 PM To: Shashwat_Nigam Cc: [EMAIL PROTECTED] Subject: RE: [ADMIN] Regarding access to a user ________________________________ > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > CC: pgsql-general@postgresql.org; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Date: Thu, 21 Aug 2008 14:23:51 +0530 > Subject: Re: [ADMIN] Regarding access to a user > > Dear Kevin > Thanks for the help. But still the user is able to see all the databases. I > defined something like this > > # IPv4 local connections: > host all all 127.0.0.1/32 md5 > host HMRI_database hmri 127.0.0.1/32 md5 You have to comment out the first entry made in your hba file. In this case it checks for the first line where all users are allowed to access all databases so it does not checks the second line. > > in the above case hmri is user and HMRI_database. But still when user is log > in as 'hmri' it is able to access all the databases. > Please provide a solution for the same. > > Thanks & Regards, > Shashwat Nigam > | Software Engineer | Geographical Information System > Satyam Computer Services Limited, Hyderabad | MOBILE: +919951467324 | > > -----Original Message----- > From: Kevin Grittner [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 20, 2008 6:41 PM > To: [EMAIL PROTECTED]; Shashwat_Nigam > Cc: pgsql-general@postgresql.org; [EMAIL PROTECTED] > Subject: Re: [ADMIN] Regarding access to a user > > >>> Shashwat_Nigam <[EMAIL PROTECTED]> wrote: > > > Now what I want is to set privilege that whenever the user log in as > Us > > he can only see database Y, none other than that. The user Us could > have all > > rights for database Y but can't go for any other database (X or Z). > > The first thing you need to do is configure "host based > authentication": > > http://www.postgresql.org/docs/8.3/interactive/auth-pg-hba-conf.html > > Among other things, this allows you to restrict which users can > connect to which databases. > > -Kevin > > > DISCLAIMER: > This email (including any attachments) is intended for the sole use of the > intended recipient/s and may contain material that is CONFIDENTIAL AND > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or > distribution or forwarding of any or all of the contents in this message is > STRICTLY PROHIBITED. If you are not the intended recipient, please contact > the sender by email and delete all copies; your cooperation in this regard is > appreciated. > > -- > Sent via pgsql-admin mailing list ([EMAIL PROTECTED]) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin ________________________________ Search for videos of Bollywood, Hollywood, Mollywood and every other wood, only on Live.com Try it now!<http://www.live.com/?scope=video&form=MICOAL> ________________________________ DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. ________________________________ Searching for weekend getaways? Try Live.com Try it!<http://www.live.com/?scope=video&form=MICOAL> ________________________________ DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
