Documentation on how to setup access on the postgresql is incomplete / missing
Bug #1883099 reported by
Wouter van Bommel
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snap Store Server |
New
|
Undecided
|
Unassigned | ||
Bug Description
In the documentation there is some talk about that a postgresql database is required and that accounts have to be created.
What is lacking in the documentation, is that various roles are used, which is important if the database is running on a different machine, and thus needs some care in the pg_hba.conf to work.
I ended up adding the following lines to the pg_hba.conf to make all the services work successfully.
host snapproxy-db snapproxy-user 10.192.64.1/32 md5
host snapproxy-db snaprevs 10.192.64.1/32 md5
host snapproxy-db snapauth 10.192.64.1/32 md5
host snapproxy-db snapident 10.192.64.1/32 md5
host snapproxy-db snapassert 10.192.64.1/32 md5
The username / role name varies, while they all access the same database.
Revision history for this message
| Marcel Drechsler (mathervenrate) wrote | #1 |
To post a comment you must log in.
I was running into a Database issue, which seems to be related to this.
I thought that the "Database-Setup" which happens when you connect the proxy to the database is enough.
Using a local DB worked though. I think this happens since the local postgresdb allows socket access, which is not as strictly configured per default as a web access to the db.
This definitely needs to be added to the documentation.