[GLASSFISH-20491] Cannot login when username and password contains German umlauts Created: 08/May/13  Updated: 19/Sep/14  Resolved: 26/Feb/14

Status: Closed
Project: glassfish
Component/s: security
Affects Version/s: None
Fix Version/s: 4.1

Type: Bug Priority: Critical
Reporter: mkarg Assignee: Nithya Ramakrishnan
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

GlassFish 3.1.1, Win 7 Pro SP1 (64 Bit), JDK 1.7.0_21


Issue Links:
Duplicate
duplicates GLASSFISH-20938 GlassFish password aliases failing Resolved

 Description   

Steps to reproduce:

  • Use JDBC realm
  • Provide user account named 'Ü' with password of 'Ä'.
  • Try to login to ACC using appclient.

Expected result:

  • Will login using user name 'Ü' and password 'Ä'.

Actual result:

  • SEVERE: Authentication or Authorization Failure

Severity:

  • As lots of people in Germany (and Austria and Switzerland) have names with German umlauts (like 'Müller'), it is really a showstopper in these countries. Think of the hypothetical case that GlassFish wouldn't accept 'th' (like 'Smith') in names in Britain or the USA, and you can imagine how upset People are over here! ;-(


 Comments   
Comment by Nithya Ramakrishnan [ 18/Feb/14 ]

Hi,

Could you pls confirm if this issue occurs with any other Realm other than JDBC realm? ALso, could you reproduce it with Authentication mechanisms like Basic Auth etc?

Thanks
Nithya

Comment by mkarg [ 19/Feb/14 ]

I do not see what this efforts should help us. We definitively need it in a JDBC realm and solely use EJB connections but not HTTP connections.

Comment by Nithya Ramakrishnan [ 21/Feb/14 ]

We wanted to isolate the issue and wanted to check if you had issues with any other usecase.
In this EJB-JDBCRealm-Apppclient setup, are you able to login successfully in case the username alone contains German umlauts and the passwords do not ? Can you pls confirm that?
ALso, can you provide the details of your database ? Have you observed this issue in more than 1 database?

This will help us get to the issue resolution faster

Thanks
Nithya

Comment by mkarg [ 24/Feb/14 ]

The problem only occurs when the password contains umlauts, while umlauts in user names work very well.

Comment by Nithya Ramakrishnan [ 26/Feb/14 ]

This issue has been resolved with a fix in Dec 3013 in Glassfish 4. Passwords with umlauts work in the appclient-EJB setup.
Could you pls try with the latest GF built from the trunk and recheck with your setup. If the bug persists, pls reopen the issue with the database details.

Comment by Tim Quinn [ 26/Feb/14 ]

The fix to GLASSFISH-20938 also resolved this problem.

Comment by mkarg [ 02/Apr/14 ]

Nithya, I cannot test using latest nightly build as you asked me for due to https://java.net/jira/browse/GLASSFISH-21027. I will test it as soon as there is a nightly build where GLASSFISH-21027 is fixed.

Comment by mkarg [ 06/Aug/14 ]

I have tested latest nightly build 4.0.1 of 2014-07-22 and hereby confirm that umlauts are working well in both account names and passwords.

Thanks for fixing this!

Generated at Thu Sep 03 06:02:17 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.