[31289] in Kerberos
Re: Does Kerberos version 5 support i18n specifications?
daemon@ATHENA.MIT.EDU (suma)
Fri Jul 10 01:00:11 2009
From: suma <suma.s.gururaj@gmail.com>
Date: Thu, 9 Jul 2009 21:25:07 -0700 (PDT)
Message-ID: <ac1ea5fe-8a7a-49b0-8369-4a4541c3492c@m11g2000yqh.googlegroups.com>
Mime-Version: 1.0
X-Complaints-To: groups-abuse@google.com
Complaints-To: groups-abuse@google.com
To: kerberos@mit.edu
Content-Type: text/plain; charset="iso-8859-1"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit
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...@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...@mit.edu
> >https://mailman.mit.edu/mailman/listinfo/kerberos- Hide quoted text -
>
> - Show quoted text -
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
