TLS Error XSOAR gui

[laurence64]

Hi All,

Bit of an odd one this, for seemingly no reason my browser started the tls client hello with tls v1 instead of v1.2 this meant that although xosar was up and running I was unable to get  to the login page as xsoar was resetting the connection, regardless of what I tried I could not fix or even pin down the issue to a root cause.

fast forward to this morning and I fired up xsoar and got to the login no problem at all, my question is, does anybody know of anything on xsoar that may have caused this or where is the best place to look? or do we just think my PC had a moment with itself and leaving it switched off fixed it ?

Cheers All,

[atullo · Accepted solution]

Since TLSv1.0 has been deprecated, not being able to login was by-design - RFC 8996: Deprecating TLS 1.0 and TLS 1.1

I'm logged into an XSOAR 6.2 instance via Chrome and went to settings (3 dots) > More tools > Developer tools > Security > Overview and was able to verify that my browser is connected via TLSv1.3:

 

[laurence64]

This is true @atullo and for very good reason as well, the issue in this case is more that I was trying to work out why the client hello was in tls1.1 as it seemed odd, and I was far from convinced that the XSOAR server would haev been requesting the downgrade, however I think the blame can be squarely aimed at a chrome/windows 10 moment of stupidity.

A rebbot did not fix it but with no action taken on the XSOAR server I could log in as if nothing had happened th following day.