Does Kerberos version 5 support i18n specifications?

[Weijun Wang]

I don't know a solution. Java uses String.getBytes("ASCII") to encode
the principal name. Unless your KDC also uses the same encoding, there's
no workaround.

Or, you can grab OpenJDK and create your own patch. :)

Max

suma wrote:
> Thanks, Max for your reply.  I appreciate it.
> 
> Until we get a solution for i18n, how are folks out there solving the
> issue of authenticating users that have nultibyte characters.  Is
> there a workaround?
> 
> Thanks in advance,
> --Suma
> 
> On Jul 10, 9:08 am, Weijun Wang <Weijun.W... at Sun.COM> wrote:
>> No support and no patch, RFC 4120 says a solution will be in future
>> revisions, and we're waiting.
>>
>> Thanks
>> Max (of Sun Java team)
>>
>>
>>
>> suma wrote:
>>> Hi,
>>> I am unable to authenticate users with non-ASCII character names.  The
>>> error that I got for kinit was:
>>> --------------------------------------
>>> Exception: krb_error 6 Client not found in Kerberos database (6)
>>> Client not found in Kerberos database
>>> KrbException: Client not found in Kerberos database (6)
>>> ------------------------------------
>>> I am using kerberos login module from JAAS for authentication.  I have
>>> no issues authenticating the users that contains ASCII.  I also
>>> checked the RFC-4120 and looks like the names to be ASCII-specific.
>>> Do I need a patch, to make my implementation support wide characters.
>>> Thanks,
>>> --Suma
>>> ________________________________________________
>>> Kerberos mailing list           Kerbe... at mit.edu
>>> https://mailman.mit.edu/mailman/listinfo/kerberos- Hide quoted text -
>> - Show quoted text -
> 
> ________________________________________________
> Kerberos mailing list           Kerberos at mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos