You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2016/07/13 13:08:20 UTC
[jira] [Commented] (DIRKRB-595) Add mode to allow KerberosString's
to contain UTF-8 for MSFT KDC interop
[ https://issues.apache.org/jira/browse/DIRKRB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374952#comment-15374952 ]
Emmanuel Lecharny commented on DIRKRB-595:
------------------------------------------
Patch applied after a bit of re-formating, with http://svn.apache.org/viewvc?rev=1752418&view=rev
Many thanks ! It might be included in the coming M23 version, which might be cut this week-end.
> Add mode to allow KerberosString's to contain UTF-8 for MSFT KDC interop
> ------------------------------------------------------------------------
>
> Key: DIRKRB-595
> URL: https://issues.apache.org/jira/browse/DIRKRB-595
> Project: Directory Kerberos
> Issue Type: Improvement
> Components: changepw
> Affects Versions: 2.0.0-RC1
> Reporter: Griff James
> Attachments: utf8-changes.patch
>
>
> By definition KerberosString's are supposed to be in the range 0x20-0x7F. MSFT's kerberos implementation breaks this rule and allows Kerberos strings to contain UTF-8 characters for I18n.
> Java's Kerberos implementation has MSFT compatibility mode which is enabled by setting the system property "sun.security.krb5.msinterop.kstring" to "true". This allows KerberosString's to contain UTF-8.
> The attached patch is a proposed change to add the same support to the kerberos-code jar to allow the change password protocol to work for users with UTF-8 chars in their principal name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)