From: | dx k9 <bitsandbytes88(at)hotmail(dot)com> |
---|---|
To: | posgres support <pgsql-admin(at)postgresql(dot)org> |
Subject: | initdb |
Date: | 2009-01-14 00:38:25 |
Message-ID: | COL120-W289F4D1F2A5F9670A145EED1D60@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I just tried initdb with the -A pam option and no -W. As expected, I can't log into the instance. There is a MD5 hash and postgres still defaults to password authentication even though I did not use the -W. Is this a bug? And I can't log into it because I have no idea what password it used. Even if I did, it's not set up how I want it to be. I want to log in with PAM.
In our company, behind the scenes pam uses openldap. It works fine adding a user with out a password still works fine. It's the postgres user that I'm concerned with. The way it is now if we change the postgres password in openldap we'd be at a loss connecting since it's using MD5.
One thing I was thinking of is using a different username for the super user like -U Tom for the initdb. Then, just adding the user postgres later via my method I know works. We add the user, just not specifiying a password. When we log in with that user the defaul goes to ldap and we can easily log in.
Maybe things have changed with version 8.3x and there is something else I should do to specifically configure ldap instead of pam. I did notice ldap in the pg_hba as an alternative method and don't remember that as a specific method before, just pam.
Thanks,
~DjK
_________________________________________________________________
Windows Live™ Hotmail®: Chat. Store. Share. Do more with mail.
http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t1_hm_justgotbetter_howitworks_012009
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-14 00:47:14 | Re: initdb |
Previous Message | dx k9 | 2009-01-14 00:08:31 | initdb |