AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() The other option is to remove KB3161608 or KB3161606 from all machines that need to access Finesse or UCCX Web Admin. TheĬipher list known to work with UCCX/Finesse 10.6 is as these: Note the restriction that the list of ciphersĪre to be used, as they cannot exceed 1023 characters in length. Instead, this should be set to EnabledĪnd the cipher suite order should be modified to exclude the twoĬiphers mentioned above. ![]() If the suite order is set to Disabled or Not Configured then the default order is used and block access to UCCX/Finesse. In order to modify the local policy through gpedit.msc Windows module, navigate to Computer Configuration >Administrative Tools >Network >SSL Configuration Settings >SSL Cipher Suite Order. Policy to exclude the ciphers in the SSL configuration. Instead, an administrator modifies the local or domain group However with IE11 there is no workaround that can be done through theīrowser. The first certificate we upgraded was the certificate on the View Broker. Here were some little issues we ran into while upgrading certificates on the Horizon Broker and the UAG Appliance. New year and some of my clients need to update their certificates for the new decade. ![]() In Firefox these can be disabled through this procedure:ĭouble click on _rsa_aes_256_sha and _rsa_aes_128_sha to set them to false. VMware UAG and Horizon Broker Certificate Gotchas in 2020. ![]() TLS_DHE_RSA_WITH_AES_128_CBC_SHA and TLS_DHE_RSA_WITH_AES_256_CBC_SHA. (TLS) cipher suites are added to the list of ones used by IE: The KB's are actually a pack of updates that installs this one in particular KB3161639 Update to add new cipher suites to Internet Explorer and Microsoft Edge in Windows.Īs you look more closely at this KB, these two Transport Layer Security I was able to work around this using the SSL Cipher Suite Order ![]()
0 Comments
Read More
Leave a Reply. |