JDK-5100603 : Need JKS KeyStore with case sensitive alias names
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 1.4.2
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-09-11
  • Updated: 2004-10-12
  • Resolved: 2004-10-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6
1.4.2_07Fixed 6Fixed
Related Reports
Relates :  
This is a continuation of 5091374. That bug allowed case sensitive aliases to be enabled via a system property. This approach is now considered unsuitable for compatibility reasons.

Instead, a new KeyStore algorithm should be added that is identical to JKS except for the case sensitive aliases. Algorithm name is TBD.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_07 1.5.0_01 mustang FIXED IN: 1.5.0_01 mustang

EVALUATION Will fix. ###@###.### 2004-09-10 The new JKS variant with case sensitive aliases is called "CaseExactJKS". If an application wants to use "CaseExactJKS" but fallback to regular "JKS" if it is not available, use code like: KeyStore ks; try { ks = Keystore.getInstance("CaseExactJKS"); } catch (KeyStoreException e) { ks = KeyStore.getInstance("JKS"); } ###@###.### 2004-09-15