[jira] [Resolved] (DIRKRB-595) Add mode to allow KerberosString's to contain UTF-8 for MSFT KDC interop

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRKRB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRKRB-595.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0-M23

Patch applied in trunk

> 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
>             Fix For: 2.0.0-M23
>
>         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)