Important! A new Community experience launched on September 26, 2017. Read more about it here or continue to Base Camp.
Voting: 
Vote up!
1 Votes
4 Replies

certificate not trusted

Linus Yong on Mar 29, 2017 21:03 EDT

Posted In
Vote up!
0 votes
Vote down!

Hello, 

Please use purvpn Paid verson its working perfect. they also offer custome solutions.

Regards.

Cris Styris

Hire Developers

Replied by: Apr 05, 2017 08:55 EDT
Vote up!
0 votes
Vote down!

Hi,

Can you please elaborate a bit more?  I am working in a corporate environment where proxy avoidance is prohibited.  Are you saying that Kony Visualizer doesn't support proxy or rather doesn't support custom CA?

 

 

Replied by: Apr 05, 2017 23:38 EDT
Vote up!
0 votes
Vote down!

Hello Linus,

 

Is it a self-signed certificate? Did you importing the certificate to cacerts of JRE which is being pointed by your kony visualizer.

You can use the java keytool commands to import the certificate to the java trust store.

 https://www.digicert.com/ssl-support/certificate-not-trusted-error.htm

 

Let me know if you still face the issue after the change.

 

Thank You,

Arif

 

Replied by: Apr 10, 2017 14:34 EDT
Vote up!
0 votes
Vote down!

Hi Arif,

Thanks for your help.  I imported the self-signed certificate into the JRE which Kony Visualizer used:

C:\Users\<<USERNAME>>\Downloads\Apps\Kony Visualizer\jre>bin\keytool -import -al
ias <<MY CA>> -keystore lib\security\cacerts -file ..\..\..\<<MY CA>>.cer
Enter keystore password:
Owner: EMAILADDRESS=<<MY EMAIL>>, CN=<<MY ORG>> Root CA, OU=
<<MY DEPT>>, O=<<MY ORG>>, L=Sydney, ST=New South Wales, C=AU
Issuer: EMAILADDRESS=<<MY EMAIL>>, CN=<<MY ORG>> Root CA, OU=
<<MY DEPT>>, O=<<MY ORG>>, L=Sydney, ST=New South Wales, C=AU
Serial number: a4ea1231237c2336
Valid from: Thu Aug 20 13:57:52 AEST 2009 until: Sun Aug 18 13:57:52 AEST 2019
Certificate fingerprints:
         MD5:  36:5C:4C:36:04:6F:F0:9E:1C:5E:FE:93:BA:DB:63:05
         SHA1: 31:EB:37:A1:CB:99:A3:78:56:44:22:AD:5F:7E:65:E1:01:2F:55:E2
         SHA256: C0:8D:DE:BC:D1:DE:DD:9C:2F:AF:03:32:23:48:58:A2:95:E4:BA:08:4B:
4C:9D:4C:7E:90:33:7B:C7:17:23:00
         Signature algorithm name: SHA1withRSA
         Version: 3

Extensions:

#1: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: 61 D5 2C 9C 1F B4 40 CE   8E 7B 9A 73 7C 74 3A E2  a.,...@....s.t:.
0010: 4F 65 8A 2E                                        Oe..
]
[EMAILADDRESS=<<MY EMAIL>>, CN=<<MY ORG>> Root CA, OU=<<MY DEPT>>, O=<<MY ORG>>, 
L=Sydney, ST=New South Wales, C=AU]
SerialNumber: [    a4ea123 1237c233]
]

#2: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
  CA:true
  PathLen:2147483647
]

#3: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: 61 D5 2C 9C 1F B4 40 CE   8E 7B 9A 73 7C 74 3A E2  a.,...@....s.t:.
0010: 4F 65 8A 2E                                        Oe..
]
]

Trust this certificate? [no]:  yes
Certificate was added to keystore

C:\Users\<<USERNAME>>\Downloads\Apps\Kony Visualizer\jre>

When I clicked on the [Login] button I get the same error that say "certificate not trusted".

Replied by: Apr 10, 2017 18:58 EDT