Opened 5 years ago

Closed 3 years ago

#125 closed enhancement (fixed)

rasgeo expects same user for postgres and rasdaman

Reported by: dmisev Owned by: HerzigA@…
Priority: major Milestone: 9.0.x
Component: rasgeo Version: 8.3
Keywords: Cc:
Complexity: Easy

Description

I think it would be better if we can separately specify postgres and the rasdaman users in the connect file?

Attachments (1)

Added-different-parameters-for-rasdaman-server-login.patch (1.4 KB) - added by abeccati 4 years ago.
add rasdaman server login parameters to config file

Download all attachments as: .zip

Change History (8)

comment:1 Changed 5 years ago by herziga@…

Hi Dimitar

do you mean we should have one user/passwd pair for connecting to RASBASE using the rasdaman API and another one for connecting to RASBASE using pq for reading/writing the meta data and raster attribute tables? I would expect those users to be identical all the time, since both connections belong to the same task. The only reason for the separate connection is that rasdaman doesn't provide an API for writing the meta data. Or could the separate connection with identical credentials cause any trouble?

Alex

comment:2 follow-up: Changed 5 years ago by anonymous

Hi Alex,

yes exactly.
The users in rasdaman are separate from those in postgres. Rasdaman assumes that the system user under which it's running has read/write access to postgres. But on top it allows you to define users to control read or write access to clients like rasgeo to rasdaman itself, not to postgres.

So usually I have a write user for rasdaman (e.g. rasadmin/rasadmin), and in postgres it's dimitar (same as my Debian user) without any password (ident authentication).

Dimitar

comment:3 in reply to: ↑ 2 Changed 5 years ago by herziga@…

Hi Dimitar

thanks for the explanation! I was always assuming that the rasdaman user and the postgres user have to be identical. I should have studied the docs more thoroughly, I guess. Now, it makes sense to me and I agree with you that there should be a way to account for that in the rasgeo connect file. We should probably align any required restructuring with Peter's suggestion to tidy up the schema, and aim for a rasgeo update, which addresses both the schema as well as the user issue. So, I think it would be best to include this discussion into the particular thread on rasdaman-dev.

Alex

comment:4 Changed 4 years ago by pbaumann

  • Milestone set to 9.0

Changed 4 years ago by abeccati

add rasdaman server login parameters to config file

comment:5 Changed 4 years ago by abeccati

  • Complexity set to Very Hard

As a starter here is a patch (also submitted 2013-08-30 11:13:38) adding the two parameters, then we have to use them in rasgeo tools accordingly: Added-different-parameters-for-rasdaman-server-login.patch

Last edited 4 years ago by abeccati (previous) (diff)

comment:6 Changed 4 years ago by abeccati

  • Complexity changed from Very Hard to Easy

comment:7 Changed 3 years ago by dmisev

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.