On Monday, January 30, 2017 at 7:16:53 PM UTC-5, Walter Rutherford wrote: > > I think that all makes sense. If I'm logging in from user 'dspace' to > 'dspace' in posgres it uses > the peer rule and lets me in without a password. Any other user would have > to be accessing > their own user/database. > So, how should the pg_hba.conf file be configured to allow any user to > access the DSpace > database via a webpage and Tomcat? > > You need an entry that matches the db.* settings in dspace.cfg or local.cfg. db.url specifies the DBMS hostname, db.username the database user, and db.password the database user's password. If your db.url is 'jdbc:postgresql://localhost:5432/dspace', db.username is 'dspace', and db.password is 'secret', then your existing 'host dspace dspace...' rule should work. The DBMS cluster would have to be on the local host and have to have a user 'dspace' with the password 'secret' for this to work.
The PostgreSQL JDBC driver always uses a TCP connection, not a local socket, so only 'host' or 'hostssl' rules will apply to DSpace. The 'psql' tool will by default use the local socket, so only 'local' rules will apply to it unless you tell it otherwise using the --host option. -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
