Bonjour Pour votre problè

Christophe Chauvet/ = 1 Août, 2005 - 17:17

Bonjour

Pour votre problème il semblerait que dans le fichier pg_hba.conf la ligne de connection contient à la fin ident sameuser, ce qui signifie, que le user au sens PostgreSQL doit aussi être un utilisateur déclaré sur le système.

Pour ne gérer les utilisateurs qu'au niveau de PG, il convient de remplacer ident sameuser par md5.

Christophe Chauvet.

ok, je vais posé le probleme

michel7/ = 3 Août, 2005 - 12:44

ok, je vais posé le probleme autrement alors :

y a t-il quelquun qui a la configuration suivante :

Fedora 4
PostgreSQL 8.0.3
PHP 5

*
*
*
*
*
*
*
*
voila ce que je trouve par defaut dan mon fichier "pg_hba.conf.sample" ( il n'y a pas de fichier "pg_hba.conf" )

* les etoiles je les rajoute sur ce message pour bien afficher mon
* message
*
*
*
*

# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the PostgreSQL Administrator's Guide, chapter "Client
# Authentication" for a complete description. A short synopsis
# follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access. Records take one of these forms:
#
# local DATABASE USER METHOD [OPTION]
# host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain socket,
# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samegroup", a database name, or
# a comma-separated list thereof.
#
# USER can be "all", a user name, a group name prefixed with "+", or
# a comma-separated list thereof. In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names from
# a separate file.
#
# CIDR-ADDRESS specifies the set of hosts the record matches.
# It is made up of an IP address and a CIDR mask that is an integer
# (between 0 and 32 (IPv6) or 128(IPv6) inclusive) that specifies
# the number of significant bits in the mask. Alternatively, you can write
# an IP address and netmask in separate columns to specify the set of hosts.
#
# METHOD can be "trust", "reject", "md5", "crypt", "password",
# "krb4", "krb5", "ident", or "pam". Note that "password" sends passwords
# in clear text; "md5" is preferred since it sends encrypted passwords.
#
# OPTION is the ident map or the name of the PAM service, depending on METHOD.
#
# Database and user names containing spaces, commas, quotes and other special
# characters must be quoted. Quoting one of the keywords "all", "sameuser" or
# "samegroup" makes the name lose its special character, and just match a
# database or username with that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect. You can use
# "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records. In that case you will also need to make PostgreSQL listen
# on a non-local interface via the listen_addresses configuration parameter,
# or via the -i or -h command line switches.
#

#@authcomment@

# TYPE DATABASE USER CIDR-ADDRESS METHOD

#@remove-line-for-nolocal@# "local" is for Unix domain socket connections only
#@remove-line-for-nolocal@local all all @authmethod@
# IPv4 local connections:
host all all ::1/128 @authmethod@
# IPv6 local connections:
host all all ::1/128 @authmethod@

*
*
*
*
*
*
*
*
puis voila ce que je trouve dans mon fichier "pg_ident.conf.sample" ( là encore il n'y a pas de fichier "pg_ident.conf" )

*
*
*
*
*
*
*
# PostgreSQL Ident Authentication Maps
# ====================================
#
# Refer to the PostgreSQL Administrator's Guide, chapter "Client
# Authentication" for a complete description. A short synopsis
# follows.
#
# This file controls PostgreSQL ident-based authentication. It maps
# ident user names (typically Unix user names) to their corresponding
# PostgreSQL user names. Records are of the form:
#
# MAPNAME IDENT-USERNAME PG-USERNAME
#
# (The uppercase quantities must be replaced by actual values.)
#
# MAPNAME is the (otherwise freely chosen) map name that was used in
# pg_hba.conf. IDENT-USERNAME is the detected user name of the
# client. PG-USERNAME is the requested PostgreSQL user name. The
# existence of a record specifies that IDENT-USERNAME may connect as
# PG-USERNAME. Multiple maps may be specified in this file and used
# by pg_hba.conf.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect. You can use
# "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# No map names are defined in the default configuration. If all ident
# user names and PostgreSQL user names are the same, you don't need
# this file. Instead, use the special map name "sameuser" in
# pg_hba.conf.

# MAPNAME IDENT-USERNAME PG-USERNAME

*
*
*
*
*
*
*
*
alors si vous avez cette configuration dites moi svp comment vous avez procédé ( notament la manipulation des deux fichiers précédents )

pour pouvoir se connecter avec un nom d'utilisateur et un mot de passe autre que ceux du system

Merci d'avance