• PKI TRAC Ticket #946 - Installation of IPA hangs up when LANG is set to tr_TR.UTF8

The first patch attempts to insure that 'UTF-8' encoding is always used when importing data from an LDIF file by replacing the Java commands which utilize the default Locale and thus potentially would override the use of 'UTF-8' when working with LDIF files.

The following ticket has been issued to address further concerns related to this issue:

• PKI TRAC Ticket #1005 - Analyze source code for Java commands which utilize default Locale and honor 'i18n'
  

The second patch specifically addresses the use of the 'tr_TR.UTF-8' issue reported in this ticket by changing the following problematic LDIF attribute names:

• index.ldif
• nsIndexType --> nsindexType
• nsSystemIndex --> nsSystemindex
• vlvtasks.ldif
• nsInstance --> nsinstance
• nsIndexVLVAttribute --> nsindexVLVAttribute
  

The root of the problem that appears to cause this issue is the use of the 'toLowerCase()' method as utilized in the LDAPJDK.  The following bug has been issued which fully describes this issue:

• Bugzilla Bug #1097868 - Proposal: Consider not honoring 'i18n' on LDAP attribute names . . . 

These patches were tested on a 64-bit Fedora 20 machine by doing the following:

• Install the patched RPMS onto the Fedora 20 test machine
  
• Set contents of '/etc/locale.conf':
• LANG="tr_TR.UTF-8"
• Reboot machine
• LANG="tr_TR.UTF-8" ssh root@fedora20.example.com
• cat /etc/resolv.conf
• ipa-server-install --setup-dns
• Choose defaults and change the BIND settings using the values from '/etc/resolv.conf'
• klist
• kinit admin
• klist
• ipa user-find
• ipa help cert
• ipa cert-show