GSSName is corrupted for non ascii chars

Hi,
I have a setup where a web application is deployed to use SPNEGO for user authentication ( using kerberos V ) and authorization.
We have several users with non english characters in the user ID and even though kerberos authentication succeeds for such users ( KDC / Active Directory is returning valid kerberos ticket which the client embeds in the SPNEGO token). Hoowever, on passing the SPNEGO token to GSS API and extracting the user name from GSS API returns incorrect user name. All non ascii characters in the user name are replaced with some junk byte sequences.
We use JGSS API (with JRE 1.4.08) for extracting the SPNEGO token and create a GSS secruity context object. Later, the GSS Name is extracted from the GSS context object.
Currently I am tesitng the SPNEGo authentication for a user with user ID 123<sp char> . The <sp char> 's unicode value is FE and UTF-8 encoded byte sequence is C3 BE. However, if I invoke 'export' method of the GSSName object and examine the returned byte sequence, instead of C3 BE, the byte sequence EF BF BD EF BF BD is present. The byte sequence for other english characters are proper.
Is this a defect in GSS-API ? Or am I not using GSS properly?
Do I need to have any special setup / configuration for using JGSS with kerberos V for users with non ascii characters in the user ID?
Please advise.
Regards,
Jayaram.
Message was edited by:
s_jayaram_s

I understand that this is an older thread.
We have spent lot of time on the internet to find out any possible workarounds or permanent solutions to enable Multi-Byte character support for username / password / SPN with Kerberos and Java . But no luck so far :(
Are there any new updates on this i18n issue ?
Thanks,
Venkatesh

Similar Messages

Non-ASCII chars in applets?

hi,
Spent 4 hours to find a way to use non-ASCII chars in applets (buttons, textareas), but didn't make it.
Simply saying
TextFieldObj.setText("\uxxxx");
//or any equivalent obj. Ex. of \uxxxx: \u015F
doesn't work. I even went into Graphics.paint() example, but it too can paint only ASCII chars.
My hunch is that it is smt. about Character.Subset but i still can't figure out how to do it.
Please SOS,
Reshat.

Hi,
I just managed to get Buttons to show Greek characters, so it appears that static buttons are fine.
However, i still face the same problem for TextField's:
TextFields work fine for IE, but in NN they sometimes convert into ASCII and sometimes give ? The same in HotJava.
So there are 2 questions in my head:
1. why can't NN use the fonts used by IE to display Non-ASCII chars?
2. What is the safest font to use for Non-ASCII chars, to cover the widest possible audience.
P.S. Java solves most cross-platform-browser problems, but the font issue still seems to be dependent on a user and his/her browser. It appears Java is not font-independent in non-ASCII context. If so, it would be nice to develop a plug-in to make sure that if the user doesn't have the font, then a Java-standardized Unicode-based font is used. Otherwise, non-ASCII world is still w/o a real Java.)
Thank you for your feedback,
Reshat.

Folders that having non-ascii chars are not displaying on MAC using JFileChooser

On MAC OS X 10.8.2, I have latest Java 1.7.25 installed. When I run my simple java program which allows me to browse the files and folders of my native file system using JFileChooser, It does not show the folders that having non-ascii char in there name. According this link, this bug had been reported for Java 7 update 6. It was fixed in 7 Update 10. But I am getting this issue in Java 1.7.21 and Java 1.7.25.
Sample Code-
{code}
public class Encoding {
public static void main(String[] arg) {
try {
//NOTE : Here at desktop there is a folder DKF}æßj having spacial char in its name. That is not showing in file chooser as well as while is trying to read for FILE type, it is not identify by Dir as well as File - getting File Not Found Exception
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
} catch (IllegalAccessException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (UnsupportedLookAndFeelException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (ClassNotFoundException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (InstantiationException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
JFileChooser chooser = new JFileChooser(".");
chooser.showOpenDialog(null);
{code}

Hi,
Did you try this link - osx - File.list() retrieves file names with NON-ASCII characters incorrectly on Mac OS X when using Java 7 from Oracle -…
set the LANG environment variable. It's a GUI application that I want to deploy as an Mac OS X application, and doing so, the LSEnvironment setting
<key>LSEnvironment</key> <dict> <key>LANG</key> <string>en_US.UTF-8</string> </dict>

UploadedFile and filenames with non-ascii chars

Hi
I'm using an UploadedFile object in my web app, and all works fine. However, when I try to upload a file, with a filename containing non-ascii chars (e.g. Spanish), I see that the getBytes method returns an empty byte array, the filename is not stored correctly (the non-ascii chars are lost, replaced by another representation), and that the content-type is application/octet-stream instead of image/png as supposed to be.
If I rename that same file to have only ascii chars - everything is back to normal.
How can I upload files with non-ascii chars in their name?

Hi, back! Spent a few hours experimenting and found
that everything is working great (including the creation
of international non-ASCII foldernames) when I used
utf-8 encoding in the sieve filters rules for the
the match strings and the folder names... at least
so far so good... for your ref and sorry for bothering.

IPhone: sectionIndexTitlesForTableView and non-ASCII chars

You specify an array of strings for your section titles in your implementation of UITableViewDataSource method sectionIndexTitlesForTableView. However, it seems like if you have a string with non-ASCII characters, it is left blank (for example the Korean string "누리마루"). Anybody else encounter this issue?

I bump Dr. Chucks thread for a similiar problem with non-ascii chars.
The chars show up but the sorting is a bit off.
Example: A, Å, B, ... Z
Should be: A, B, ... Z, Å, Ä, Ö
In Swedish Å (the letter Aring;) is one of the last letters and should not be placed after A despite being similiar.
Any ideas?

FILE_DATASTORE and non-ASCII chars

I have created an interMedia Text index
with the FILE_DATASTORE option, so that
interMedia treats table entries as
filenames and indexes the corresponding
file on the servers's filesystem.
But whenever the filename contains characters
which are not part of the US7ASCII charset (like dv| _), the file is not found. But both Oracle and the operating system support these characters.
The Oracle instance uses UTF8 as internal
characterset. The client which stores
the filenames in the table uses the
WE8ISO8859P1 charset. The values in the
database table are stored and shown correctly
when viewed with Oracle or Java client
programs.
So where does the charset conversion fail ?
The names are stored correctly, they can be
read correctly by clients, but the indexer
seems to use a wrong charset to translate
the filenames stored in the database into
filenames of the operating system.
Do I have to apply some additonal configurations to my indexer ?
Greetings,
Michael Skusa
null

I bump Dr. Chucks thread for a similiar problem with non-ascii chars.
The chars show up but the sorting is a bit off.
Example: A, Å, B, ... Z
Should be: A, B, ... Z, Å, Ä, Ö
In Swedish Å (the letter Aring;) is one of the last letters and should not be placed after A despite being similiar.
Any ideas?

Can Java be started in a directory that contains non ascii char

I installed a product developed using Java in a folder whose name contains non-ascii chars, such as Japanese chars or german chars.
This will cause error said: unable initialise java virtual machine, error code -1
Some one said Java doesn't like being started in a directory that contains non ascii characters. There appears to be no way of passing it unicode parameters.
Is there anyone once hit the similiar issue or know the root cause of such problem?
Thanks

Yes you can use your web start application console. To enter data which is required for your application it is better idea to use java application which runs in console mode althou you may try to run console of windows and then read data from its input stream.

How Aperture encodes non-ascii chars

It looks like Aperture uses a way of encode chars as UTF that seem to be bit unusual, many application (especially web apps) expects another way of encoding Unicode chars. The end result is that non-ascii chars comes out really strange.
When I use applescript to read the IPTC info I need to do something like this before using the data:
set c_title to normalize unicode p_title without decomposition
Is there some way of telling Aperture to do this automatically when exporting photos?
(sorry about the bad use of Unicode terminology but I don't know the area very well)

I've spent quite a bit of time on this topic - I'm the author of Phoshare http://code.google.com/p/phoshare/, an open-source tool to export images and metadata from iPhoto and Aperture. Storing non-ASCII characters in image metadata is a messy business. If you want to get a taste of it, have a look at the Exiftool FAQ at http://www.sno.phy.queensu.ca/~phil/exiftool/faq.html#Q10 . A quote: "Most textual information in EXIF is stored in ASCII format, ... However *it is not uncommon for applications to write UTF‑8 or other encodings where ASCII is expected*". This leads to all sorts of problems, because the reader will have to make assumptions about the encoding used by the writer.
In the case of Aperture, I have found that it writes metadata encoded in a way consistent with what most other applications and on-line services expect. Most of the encoding problems I've debugged where caused by bad input data. E.g. the characters were encoded improperly to begin with, but in a way that they still display as expected in some places (like Aperture). Can you try erasing some of the meta data in Aperture, and retype them from scratch (e.g. not copy-paste, which would paste the same stuff right back). Also make sure that you force-updated the preview images, so that the new meta data get written into the files.

Java 5, Linux, 64-bit: Non-ASCII chars over socket

Hi,
I am having issues with reading non-ASCII chars from a socket. I send a mixed message, with the first part in ASCII and the last bit in non-ASCII. There are no issues with reading the non-ASCII characters on Windows. However, when I try running the server on Linux. The following is a message sample:
Start message<CRLF>
фвафывафвыафыв<CRLF>
The second part (which is encoded in either Windows-1250 or KOI8-R), comes out as 3F (when you look at the bytes) on Linux.
Any suggestions?
Thanks,
Max

You must be using Readers and Writers, and you need to make sure you specify the same charsets when constructing them. Don't leave this to the default, as this seems to vary across platforms and definitely has varied across releases.

What is current CommSuite support for non-ASCII passwords?

Hello all,
Some of our users managed to change their passwords to non-ASCII strings (via replication from MSAD by ISW) and no longer have access to their communications services.
While replicating the problem, I have set a (UTF-8 non-ASCII) string as my password in DSEE directly, and *can* log in to Convergence with this password. However, if I change the working password to a non-ASCII string from Convergence itself - it is accepted during the secondary password check, there is no error returned, SOME password is apparently saved into the LDAP directory, but neither of the original non-ASCII plaintext strings can be used for login back into Convergence. Restoration of access is only doable by admin at this point.
Checking email by IMAP from Thunderbird no longer works with a changed non-ASCII password (including the state when it still works for Convergence).
Delegated Admin has an explicit check for non-ASCII characters in the password and refuses to set a misbehaving one.
I see that among the standards supported by CommSuite, there is IMAP4rev1, and RFC 5255 refers to it as the reason that non-ASCII passwords and usernames are for now not supported, though this is expected to be a temporary state of things, and software can prepare for the future by implementing checks for valid UTF-8 strings as well.
https://wikis.oracle.com/display/CommSuite/Messaging+Server+Supported+Standards
http://tools.ietf.org/html/rfc5255
5.1. Unicode Userids and Passwords
   IMAP4rev1 currently restricts the userid and password fields of the
   LOGIN command to US-ASCII. The "userid" and "password" fields of the
   IMAP LOGIN command are restricted to US-ASCII only until a future
   standards track RFC states otherwise. Servers are encouraged to
   validate both fields to make sure they conform to the formal syntax
   of UTF-8 and to reject the LOGIN command if that syntax is violated.
   Servers MAY reject the LOGIN command if either the "userid" or
   "password" field contains an octet with the highest bit set.
   When AUTHENTICATE is used, some servers may support userids and
   passwords in Unicode [RFC3490] since SASL (see [RFC4422]) allows
   that. However, such userids cannot be used as part of email
   addresses.
So, the main question at this point is: does or does not all of the CommSuite stack support non-ASCII passwords?
If no - please confirm, so we can instruct the users to not create problems for themselves (and maybe manage to set up some policy to not accept non-ASCII passwords to MSAD/DSEE in the first place).
If yes - what should be done to enable support in Convergence/IMAP/SMTP/XMPP/WCAP/WABP/... services - perhaps, setting the LANG/LC_ALL locale environment variables or equivalent JVM flags for UTF-8 in server startup scripts, etc.? (I know that DSEE ldapsearch requires either envvars or a command-line flag for charset encoding of values, so I figure similar quirks may be relevant for some other software)
Thanks in advance for either response,
//Jim Klimov

I can't respond for the suite, but the Messaging Server product should work with UTF-8 usernames and passwords as long as the standard SASL authentication mechanisms that are documented to use UTF-8 are used (e.g. SASL PLAIN). IMAP LOGIN may work fine with UTF-8 as well even though that's non-standard. We do not implement SASLprep, however, so the strings provided by the client to the server must be identical UTF-8 strings for authentication to succeed. If they are provided in a different decomposition, different canonical form or non-standard charset, that's not supported and will fail. We don't test this scenario extensively, so you may encounter bugs (that we'd have to prioritize and fix as with other bugs). Messaging Server recently implemented a restricted option (broken_client_login_charset) for a customer who was stuck with broken clients that sent ISO-8859-1 for the IMAP login command arguments.

Does Java 5 accept non-ascii chars as identifiers?

I am surprised to find out that Java 5.0 accept non-ascii chars as identifiers.
Is it true that Java 5 really accept non-ascii chars?
Thanks.

Here is the code:
public class non��name {
private static void ��(){
    System.out.println("this is called from a function with a chinese name!");
    int ��1 = 1, ��2 = 2;
    System.out.println("��1 = " + ��1 + ", ��2=" + ��2 + ", �� = " + (��1+��2));
public static void main(String[] args) {
    ��();
}

Validation for non-ASCII characters

Hi all,
Requirement: I have to apply a validation on on fields like Name and Address in applicationdefination.xml. When a user types non-ASCII characters and navigates to next page then it should display the error message. Thus, I have to restrict my user to ASCII values only.
Present Situation: I'm using regular expression for this problem. In Jheadstart there is an option regular expression under the heading Validation. I have written following values in regular expression and Regular Expression Error Message options.
Regular Expression
^\s*[\w\.\,\-\_\#\'\/\\\ u0022\u0026\*\;\:\s]+\s*$
Regular Expression Error Message
It is important to note that foreign characters are not accepted on our system. Please ensure only standard English letters are entered
Since, i was getting error in jspx page due to double quotes(") and ampercent(&), So i have replaced the double quotes(") and amprecent(&) by their unicodes. Thus, the expression has become like ^\s*[\w\.\,\-\_\#\'\/\\\u0022\u0026\*\;\:\s]+\s*$.
This expression is validating many characters like Ã,µ,Ç,Ï,Ö,§,¥,{,} but not all non ASCII characters like ѓ є ѕ ї Њ Щ Ώ Ω Ϊ Ά Ή Θ Λ Ξ Π τ ẫ ờ Ỡ Ứ Ỷ ự Ẁ ỹ ị Ọ ň ũ ť ţ Έ Ϊ ﻍ. Thus, its not fulfilling the requirement.
Please suggest some valid solution to this problem. It’s very urgent.

Hi,
The validation seems to be performed in Java or Javascript depending on the layout (I'm sorry I can't remember the exact details). The expression suggested above by theEternalStudent works very well in Java, but not in Javascript.
We came up with an expression which works in both. It rejects strings which contain &# by doing a lookahead before the main pattern - you might want to expand this to look for &#nnn; but for our purposes &# is enough.
Here is the "platform neutral" solution:
(?!.*\u0026#.*)^[\w\.\,\-\_\#\'\/\\\u0022\u0026\*\;\:\s]+$
I think in future we will write a javascript function and amend the templates to call it directly.
thanks,
Michael

Can ims5.2p1 do sieve filter searches with non-ASCII chars?

Particularly, is it possible with the
Subject header line, which is
=?xxx?Q?xxxxx?= or =?xxx?B?xxxxx?= encoded
Resolved the fileinto foldername part, but
now found that seems like ims's sieve filter
cannot do non-ASCII matches... Thanks.

Hi, back! Spent a few hours experimenting and found
that everything is working great (including the creation
of international non-ASCII foldernames) when I used
utf-8 encoding in the sieve filters rules for the
the match strings and the folder names... at least
so far so good... for your ref and sorry for bothering.

How to create a native KeyEvent for non ASCII characters

Hello
i need to create a native KeyEvent with my application. I know that it is possible to send such a event with the Robot-Class. But how do i send an event for a none ASCII character such as the german � (O with Diaeresis)?
I also know that a combination of KeyEvent.VK_DEAD_DIAERESIS + KeyEvent.VK_O will get me the desired result, but i want just to pass the charachter � and let Java create the correct KeyCode(s).
Does anyone knows a solution?
BTW: AWTKeyStroke always returns 0 for the �
Thanks
Matt

Hi, James.
Unfortunately, none of the F-keys can be set to the functions of the Volume keys using the Keyboard Shortcuts preference pane.
Mac OS X does not include native support for assigning a macro or script to either an Fkey or other keyboard shortcut. For that, you need a third-party tool, like iKey, Quickeys, or Spark, the latter suggested by DPSG-Scout.
You'd also need a set of scripts to assign to the keys, e.g. scripts to increase, decrease, or mute the volume. Those are tricky to write since System Preferences does not expose much to AppleScript. One would need to use the "GUI Scripting (System Events)" technique to create a script to change the settings in the Sound preferences pane of System Preferences.
Automator does offer a "Set Computer Volume" action, which allows you to adjust the various Volume settings (Output volume, Alert Volume, Input Volume) to a specific set of levels, including Mute for Output Volume. However, it won't handle the idea of pressing the same key multiple times to either increase or decrease the volume, ala the Volume Adjustment keys. In your case, it's most useful for Mute. Automator Workflows can be saved as applications, which I believe can then be assigned to Fkeys in iKey or QuickKeys.
Someone may have written a more advanced Automator action for adjusting volume than that provided with Mac OS X. Search Apple's Automator Action Downloads. If you find one, instructions on adding actions to Automator can be found in Automator Help.
You could search ScriptBuilders to see if someone has already written scripts for the functions you need, then use iKey or Quickeys to assign such to keyboard shortcuts.
Finally, you could solve the problem another way: buy a set of external speakers that has its own separate volume and mute control. For example, my trusty old Monsoon MM1000s have their own volume control with a mute button.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

Page encoding / charset / special chars / NON-ASCII chars

Whenever special characters are used in our environment, the data is stored incorrect ...
® gets converted to Â®
and other special chars gets converted to other special chars ... the strange thing is that some inputText fields in some pages work just fine ..chars dont get converted and it happend in some other many pages ...not sure whats going on ..I tried to change the charset or the pageEncoding of the pages or even manually using the setPageEncoding in the reequest and in the response ..with no luck ...when I print the request params ..the values are converted, so ma not sure at what stage the string get converted and how to prevent it ...
Charset of the jsp-page is UTF-8. Need help here please.
Thanks.

You must verify that all resources are in UTF-8. There are a couple of places you have to check:
Compiler encoding
Embedded OC4J JSP Compiler options
Project settings
After that it worked for me.
Timo

GSSName is corrupted for non ascii chars

Similar Messages

Maybe you are looking for