I did that doc word for word (Even several times) and workbench is not allowing me to connect from my workstation but it works using HTTPS on the server itself.
Point to be noted : Ensure that you connect to HTTPS by using the name that is specified in the certificate. This name is typically the fully qualified host name.
The name specified in the cert is the host name only and not the full qualified domain name. Does it really have to be the FQDN instead.?
In server settings(Workbench), you should provide the hostname as there in your certificate(i.e. hostname + domain).
Everything matches. Cert is hostname and the server settings(Workbench) is hostname as well.
Check whether certificate has been imported inside cacerts keystore successfully, use keytool -list -keystore <Path to cacerts> | more
it looks like it did.
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
ServerName, Jun 5, 2013, trustedCertEntry,
Certificate fingerprint (MD5): (Entry)
Could u plz confirm the path to cacerts ? Bcz there are many trusted certificate already present by default but u have only one entry !!
E:\Program Files (x86)\Adobe LiveCycle Workbench ES3\workbench\jre\lib\security
Does it matter whether the certifcate is for HOST name and the FQDN?
I already did that and still doesn't work. Thanks
You can try the below steps if you are using jBoss app server.
1.Open the secured adminui url (https://localhost:8443/adminui/) in the browser (ie explorer) .
2.It will give you the certificate error. Import that certificate by going to detail tab -> copy to file-> next-> select option DER encoded binary x.509 .cer
3. Save the above cert file to your local machine where workbench is installed.
4.Now run the below command
5.keytool -import -file “path of the above cert file on your machine including the cert name" -keystore "C:\Program Files (x86)\Adobe LiveCycle Workbench ES4\workbench\jre\lib\security\cacerts"
6.it will ask for password , which is changeit
7.it will ask if you trust this certificate , type Y then enter
8.Now your secured https certificate is imported to the cacerts file present in the security folder of workbench.
9.Restart the workbench, and before logging , configure the workbench login portal by providing below details
b)Protocol : select the secured one (soap/https)
c)Port number will be : 8443 (for jBoss)
10. Try logging.
I know this is old, but I have tried all the steps in this thread, plus rebooting my workstation, and I am having the same problem. Has anyone found a solution to this problem?
In case anyone ever runs into this problem in the future, the solution for me was to delete the jre folder within the workbench folder, and replace it with the latest jre downloaded straight from Oracle. Then I imported the certificate into the cacerts file. Originally I had installed java through the workbench interface, but it seems like it may have been using an old version. Hope this helps someone.
Sorry to bump this old thread, but I am also having this issue. I have:
- followed the steps to import the certificate into the cacerts used by workbench
- ensured i used the FQDN in workbench properties that match certificate
- restarted system
- no luck
- replaced entire jre folder in workbench path as suggested above
- re-imported the certs
- still no luck
Browser access over https works just fine. I'm stuck here. Any other ideas from anyone?
Did you obtain a solution to the issue regarding the public key certificate and launching Workbench as https. I am also getting the same error and have tried all steps on the forum.