Cipher Tool throws java.nio.file.InvalidPathException: Illegal char <:> in Windows
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 41
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
Description:
Cipher Tool v1.0.0-wso2v8 throws java.nio.file.InvalidPathException: Illegal char <:> in Windows environment.
Affected Product Version:
EI 640
ISKM 570
IS 570
AM 260
OS, DB, other environment details and versions:
Windows
Steps to reproduce:
Unzip the any of product mentioned above in a windows environment.
Goto <carbon_home>/bin direcotry.
run the command "ciphertool.bat -Dconfigure"
Exception
Using JAVA_HOME: C:\Program Files\Java\jre1.8.0_181
Exception in thread "main" java.nio.file.InvalidPathException: Illegal char <:> at index 25: C:\wso2\wso2ob-ei-6.4.0\C:\wso2\wso2ob-ei-6.4.0\/repository
/resources/security/wso2carbon.jks
at sun.nio.fs.WindowsPathParser.normalize(Unknown Source)
at sun.nio.fs.WindowsPathParser.parse(Unknown Source)
at sun.nio.fs.WindowsPathParser.parse(Unknown Source)
at sun.nio.fs.WindowsPath.parse(Unknown Source)
at sun.nio.fs.WindowsFileSystem.getPath(Unknown Source)
at java.nio.file.Paths.get(Unknown Source)
at org.wso2.ciphertool.utils.Utils.getConfigFilePath(Utils.java:98)
at org.wso2.ciphertool.utils.Utils.setSystemProperties(Utils.java:289)
at org.wso2.ciphertool.CipherTool.initialize(CipherTool.java:93)
at org.wso2.ciphertool.CipherTool.main(CipherTool.java:52)
Related Issues:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Utils.java at getConfigFilePath(Utils.java:98), reached by running ciphertool.bat -Dconfigure from the product's <carbon_home>/bin directory on Windows. Reproduce the failure and verify that the generated security keystore path no longer contains the duplicated Windows drive prefix and that initialization completes without InvalidPathException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100