headers
Torsten Bronger | 18 Jun 2011 21:07
X-Face
Picon
Picon
Picon
Picon
Favicon
Gravatar

Problems with adduser

Hallöchen!

I use RefDB SVN-747 with PostgreSQL.  With refdba, I experience the
following:

bronger <at> wilson:~$ refdba -u chantal
Please enter your password:
refdba: listuser -d biblio
main database version is not supported
refdba: listuser -d biblio
chantal
drefdbuser1
refdb
999:3
refdba: adduser -d biblio toll
238:toll:biblio
999:1 added:0 failed
refdba: listuser -d biblio
chantal
drefdbuser1
refdb
999:3

(The first "main database version is not supported" is stange
because a second try works.  But this is not the main reason for my
posting.)

My problem is that I cannot see the user "toll" after having added
him.  The user "chantal" is allowed to add new users.  And what does
"238 - revoke user permissions successful" mean in this context?
(Continue reading)

Permalink | Reply |
headers
Markus Hoenicka | 19 Jun 2011 00:49
Picon

Re: Problems with adduser

Quoting Torsten Bronger <bronger <at> physik.rwth-aachen.de>:

> Hallöchen!
>
> I use RefDB SVN-747 with PostgreSQL.  With refdba, I experience the
> following:
>

Hi,

which PosgreSQL server version do you use? I did not have time to  
catch up with the latest PostgreSQL releases. My first guess is that  
there are some subtle changes in the database engine's access control  
which RefDB does not handle gracefully.

The 238 status message in this context simply confirms that the ALTER  
GROUP ADD USER SQL query ran successfully.

Right after adding a user, it does not show up in the listuser output  
because of the way RefDB checks for the presence of a user. It does  
not query the database engine's access control because some engines do  
not have such a thing. Instead, RefDB checks whether or not the  
requested user has entries in the reference database. So you should  
think of the listuser output as "users that have entries" rather than  
as "users that have access".

regards,
Markus

--

--
(Continue reading)

Permalink | Reply |
headers
Torsten Bronger | 19 Jun 2011 10:29
X-Face
Picon
Picon
Picon
Picon
Favicon
Gravatar

Re: Problems with adduser

Hallöchen!

Markus Hoenicka writes:

> [...]
>
> which PosgreSQL server version do you use?

8.4.8

> [...]
>
> Right after adding a user, it does not show up in the listuser
> output because of the way RefDB checks for the presence of a
> user. It does not query the database engine's access control
> because some engines do not have such a thing. Instead, RefDB
> checks whether or not the requested user has entries in the
> reference database. So you should think of the listuser output as
> "users that have entries" rather than as "users that have access".

My Web frontend creates RefDB users for every user which is added to
the Web frontend.  My idea was to check with "listuser" whether a
user is already in the references DB.  If this doesn't work, is it
okay to add a user (possibly) multiple times?

Besides this, if I use "adduser", the new user appears amongst the
"login roles" of PostgreSQL, but not in the t_user table.  This is
not correct, is it?

Tschö,
(Continue reading)

Permalink | Reply |
headers
Torsten Bronger | 19 Jun 2011 11:09
X-Face
Picon
Picon
Picon
Picon
Favicon
Gravatar

Re: Problems with adduser

Hallöchen!

Markus Hoenicka writes:

> [...]
>
> [...] So you should think of the listuser output as "users that
> have entries" rather than as "users that have access".

After some further testing, I now see what you mean, so ignore my
previous posting.  And adding an existing user with the same
password seems to be idempotent.  Howerver, password changes don't
happen, at least not in Postgres.

Tschö,
Torsten.

--

-- 
Torsten Bronger    Jabber ID: torsten.bronger <at> jabber.rwth-aachen.de
                                  or http://bronger-jmp.appspot.com

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
Permalink | Reply |

Gmane