Description
Generally speaking, the CLI works with standard https sites like Cloud. However, you may have an internal site or other that runs into various HTTPS/SSL problems. The most common cause is using self-signed certificates. They can be solved, but, each requires some problem determination and finding the solution that works for you. The CLI is implemented in Java and some of the resolutions have to do with telling java how to work with the security involved with the system you are trying to access in a proper way. This describes some of the common problem symptoms and links to help resolve. Often using google with your error is the best way to find some help in this area.
Links
- SSL Exceptions while using CLI Add-ons
- Use JIRA CLI with SSL
- HTTPS and SSL related issues for CLI products
- Adding self-signed https certificates to Java keystore
- How to properly import a self-signed certificate into Java keystore that is available to all Java applications by default?
Common problems
...
| autoNumber | true |
|---|
...
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
...
...
ACLI-188Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 729d679a-302c-339f-958b-015e107badcd key ACLI-188
...
Resolution (from user):
This was an Apache configuration problem per https://community.qualys.com/thread/13532.
We needed to add a ServerName setting.
Still having problems?
...
| Include Page | ||||
|---|---|---|---|---|
|