Discussions
Categories
- 197.1K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 555 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.3K Development
- 17 Developer Projects
- 139 Programming Languages
- 293K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 158 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 468 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
keytool won't allow me to genkeypair for older keystore with 5-character password

I have an older keystore with a 5-character password. It was last updated in 2014, probably with the 1.5 or 1.6 version of keytool. Current versions of keytool insist that all passwords be at least 6 characters long.
Anyway, this keystore can be opened successfully by our app using the 5-character password, and I can use that password and the -list command to display the contents. However, when I try to generate a new key pair, keytool won't accept the valid 5-character password. It throws the error "keytool error: java.lang.Exception: Key password must be at least 6 characters".
I can understand that error being thrown when creating a new keystore, but keytool should allow me to update an existing keystore, regardless of the password length. Does anyone know of a workaround to force current versions of keytool to be backwards-compatible with this older keystore? I'd like to avoid creating a new keystore from scratch.