On Wed, Aug 06, 2008 at 10:10:31AM -0400, Kieffer, Paul wrote: > [EMAIL PROTECTED] dspace-1.5.0-build.dir]$ psql -U dspace -W -h localhost > Password for user dspace: > psql: FATAL: Ident authentication failed for user "dspace"
It appears that PostgreSQL is set up to use Ident authentication when a connection to database "dspace" is requested by user "dspace", and that this is failing. Does the host run an Ident service? Ident authentication means that the DBMS will ask a network service on the client host, "what user owns the process which is connecting to me on this socket" and compare the reply with the client's claim. Ident is almost never the best way to authenticate, because it's not reliable in the general case. To answer your question directly: the PostgreSQL administrator (or "superuser") can set any user's password. This user account will have been created when the database cluster was created with 'initdb', so I hope that someone knows what the account was named and what password it was given. Like most DBMS, PostgreSQL has its own accounts table independent of that used by the OS, so passwords and even account names may not correspond between DBMS and OS. However, none of this has anything to do with "Ident" authentication, except that the claimed user account name must name an account in the DBMS' accounts table. The easiest authentication method to get working is "trust", but this is dangerous: "trust" authentication accepts the user's claim of identity without any proof -- no password, no Ident check, nothing. I would use "trust" only until I got something safer to work. I typically use "md5" authentication. This is based on passwords and will be familiar to most. It's probably a good method to replace "trust" as you are setting things up. If you have central identity services such as Kerberos or an LDAP directory, and you want to use those, Pg supports them. Pg can also call out to PAM for authentication if you want to go that route. All of these are more complicated to configure than the methods mentioned above, and I wouldn't recommend them until you are more familiar with running PostgreSQL. Authentication is set up in the file pg_hba.conf in the database cluster's home directory. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
pgpsoBM5LjgV2.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
