SSL Client Certificate Auth - Works in Firefox but not Chrome or IE

Forums › IT Pro and developers › SSL Client Certificate Auth - Works in Firefox but not Chrome or IE

1 | 2

ajobbins

5053 posts

Uber Geek
+1 received by user: 1280

Trusted

#1512211 13-Mar-2016 10:13

timmmay:

Probably not, but it will give more information. I know my servers were generally more compatible and worked with more browsers when I added TLS 1.1 and 1.0 than when I was 1.2 only.

Yes, I've gone with TLS1.2 for the highest security. As it's exclusively for my own use I have no need to support legacy tech.

Nonetheless, last night I did try both TLS1.1 and 1.0. Exactly the same result.

Twitter: ajobbins

timmmay

20923 posts

Uber Geek
+1 received by user: 5395

Trusted

Lifetime subscriber

#1512216 13-Mar-2016 10:37

Assume you googled the error message and found this post on SF? One suggestion is to try disabling TLS1.2. Again it's just diagnosis, not suggesting you stay like that.

insane

3329 posts

Uber Geek
+1 received by user: 1009

ID Verified

Trusted

2degrees

Subscriber

#1512223 13-Mar-2016 11:16

Try going to https://www.howsmyssl.com/ and check the difference between the browsers and add whatever Cipher to your config that you're missing.

mentalinc

3403 posts

Uber Geek
+1 received by user: 1035

Trusted

#1512224 13-Mar-2016 11:16

Use ssllabs.com as I posted earlier.

under "Handshake Simulation" it has the various versions of Android

If you have version 4.4.2 of android on your device or greater you should be fine.

Happy to have you pm the url you having issues with.

CPU: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB: Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440

Quic: https://account.quic.nz/refer/473833 R473833EQKIBX

ajobbins

5053 posts

Uber Geek
+1 received by user: 1280

Trusted

#1512225 13-Mar-2016 11:34

OK I have resolved it. I'm not 100% sure this is what it was, but when I created the initial key pair for the client cert, I used 2028 bits instead of 2048 (Assume a typo in the guide I was following).

I generated a new cert with 2048 instead and it's all working now. Guess Windows was fussier about it than other things were.

Twitter: ajobbins

1 | 2