Обсуждение: Authentication failed when Password contains Japaneese Charecters

Shivender Devarakonda <shivenderd@gmail.com> writes:
> I am using Postgres SQL version 8.3 server and I have a client that uses
> Postgres SQL JDBC driver. I have a user "admin" with the password having
> japaneese charecters 形式.

Just a guess, but I suspect it's an encoding issue.  I expect JDBC would
send the password in utf8 encoding.  Maybe you defined the password in
a session that was using a different encoding?

            regards, tom lane

Shivender Devarakonda <shivenderd@gmail.com> writes:
> I did not give any explicit encoding while creating the DB. I am running
> postgres on Windows XP system.

Well, you should look at what server_encoding is set to, then.
If it's not UTF-8 then that's likely the source of the problem.

            regards, tom lane

>
>
>Shivender Devarakonda <shivenderd@gmail.com> writes:
>
>
>>> I am using Postgres SQL version 8.3 server and I have a client that uses
>>> Postgres SQL JDBC driver. I have a user "admin" with the password having
>>> japaneese charecters 形�.
>>
>>
>
>Just a guess, but I suspect it's an encoding issue.  I expect JDBC would
>send the password in utf8 encoding.  Maybe you defined the password in
>a session that was using a different encoding?
>
>            regards, tom lane
>
>
>
Encoding I think is the best guess, but I did have a password that
worked perfectly
well with psql but failed in the application using the JDBC. I finally
tracked it down to
a special escape sequence character, %, in the password string created
by a user. You
could check to make sure one of your character encodings does not
translate to one
of these special characters. Solution finally was to translate the
character to a
hexadecimal value. Code follows:

// MySQL, PostgreSQL, & HSQL
else
{
// The % character is interpreted as the start of a special escaped
sequence,
// two digit hexadeciaml value. So replace passwordString characters
with that
// character with that characters hexadecimal value as sequence, %37. Java
// API URLDecoder.

passwordString = passwordString.replaceAll("%", "%" +
Integer.toHexString(37));
connectionProperties += subProtocol + "://" + host + ":" + port + "/" +
db + "?user=" + user
+ "&password=" + passwordString + "&useSSL=" + ssh;
// System.out.println(connectionProperties);
dbConnection = DriverManager.getConnection(connectionProperties)
}

danap.

Shivender Devarakonda <shivenderd@gmail.com> writes:
> When I did the psql -l I see the following DBs in my local environment:
> C:\PostgreSQL\bin>psql -l
>         List of databases
>    Name    |  Owner   | Encoding
> -----------+----------+-----------
>  cmdb     | admin    | UTF8
>  postgres  | postgres | SQL_ASCII
>  template0 | postgres | SQL_ASCII
>  template1 | postgres | SQL_ASCII

> I am using cmdb which is UTF8.

Hmm, but which database did you connect to when you set the user's
password?

            regards, tom lane

I connect to cmdb

-Shivender
Sent from my iPhone

On Apr 20, 2010, at 8:49 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Shivender Devarakonda <shivenderd@gmail.com> writes:
>> When I did the psql -l I see the following DBs in my local
>> environment:
>> C:\PostgreSQL\bin>psql -l
>>        List of databases
>>   Name    |  Owner   | Encoding
>> -----------+----------+-----------
>> cmdb     | admin    | UTF8
>> postgres  | postgres | SQL_ASCII
>> template0 | postgres | SQL_ASCII
>> template1 | postgres | SQL_ASCII
>
>> I am using cmdb which is UTF8.
>
> Hmm, but which database did you connect to when you set the user's
> password?
>
>            regards, tom lane

Try change the encoding of sesssions at database nivel to UTF8; this
encoding is taked as default for sessions
http://www.postgresql.org/docs/8.1/static/sql-alterdatabase.html ; try
ALTER DATABASE databasename SET ENCODING TO 'UTF8'
(or maybe UFT8 directly).
or if this don't work try
ALTER DATABASE databasename SET client_encoding TO 'UTF8'
or.... from Java set the econding of connections on creation or
configuration time (I don't know where exactly, but sure it's possible).

Shivender Devarakonda escribió:
>
> When I did the psql -l I see the following DBs in my local environment:
>
> C:\PostgreSQL\bin>psql -l
>         List of databases
>    Name    |  Owner   | Encoding
> -----------+----------+-----------
>  cmdb     | admin    | UTF8
>  postgres  | postgres | SQL_ASCII
>  template0 | postgres | SQL_ASCII
>  template1 | postgres | SQL_ASCII
>
> I am using cmdb which is UTF8.
>
> I think it is consistent with my application? any thoughts what might
> be wrong.
>
> Thanks,
> Shivender
> On Tue, Apr 20, 2010 at 7:07 PM, Shivender Devarakonda
> <shivenderd@gmail.com <mailto:shivenderd@gmail.com>> wrote:
>
>     Thanks. Where should I look for this property?
>
>     Thanks,
>     Shivender
>
>
>
>
>     On Tue, Apr 20, 2010 at 6:18 PM, Tom Lane <tgl@sss.pgh.pa.us
>     <mailto:tgl@sss.pgh.pa.us>> wrote:
>
>         Shivender Devarakonda <shivenderd@gmail.com
>         <mailto:shivenderd@gmail.com>> writes:
>         > I did not give any explicit encoding while creating the DB.
>         I am running
>         > postgres on Windows XP system.
>
>         Well, you should look at what server_encoding is set to, then.
>         If it's not UTF-8 then that's likely the source of the problem.
>
>                                regards, tom lane
>
>
>

Shivender Devarakonda <shivenderd@gmail.com> writes:
> I set the following property  in postgresql.conf:
> client_encoding = UTF-8  # actually, defaults to database

That would not help if you were connecting to a database with SQL_ASCII
encoding (which defeats all encoding intelligence).  I'd suggest
connecting to cmdb with psql and issuing an ALTER USER command to
set the user's password again.

            regards, tom lane

Shivender Devarakonda <shivenderd@gmail.com> writes:
> I tried to use ALTER USER to change the password, for some reason the sql
> command is not displaying the japaneese charecter properly and I tried using
> the buffer file but the buffer file was default to ANSI format and it is not
> accepting UTF-8 format..

Well, that's sure consistent with the idea that you've got encoding
conversion issues going on.  I don't know enough about encoding behavior
on Windows to help you much more with that.  The path of least
resistance might be to use a plain-ASCII password.

            regards, tom lane