i am installing IDC from ipics 4.5.2 on my PC
but i can not login because there is certificate issue.
how can i get the certificate from ipics server?
here is the error
Hi Gilbert, I have this same issue. Still working on it but the LCCMreport.log shows this (ip address removed).
Cisco.PSBU.Exceptions.ServerException: Error logging into server x.x.x.x(x.x.x.x) ---> System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
Furthermore I have uninstalled/reinstalled the IDC several time but it NEVER asks for a certificate like it is supposed to when logging in the first time.
CiscoTAC mentioned that removing Windows Update KB3172605 may help since it is tied to certificate validation. It did not solve my problem but maybe it will for you?
All the usual culprits ruled out? (Time sync between server and client mismatch, etc...). I'm not familiar with
Thx Scott. I do not think that is the issue. Whats worse is that is was working on my PC just fine this summer (over SSL VPN and a different time zone). I think we are dealing with a MS office issue. I plan to uninstall all updates on a test PC later on today.
What's the details on the actual certificate being presented from the server? Perhaps it's just no longer valid / has been impacted or implicated in a security update from MS (as you suspect).
So you were on the right track. Here is the fix for the login error I had.
Just for your awareness, here is the defect opened about the windows patch I mentioned when we started this case. It certainly sounds like a match for your problem. I am also including a workaround being used for some of our other products. You might try this workaround and see if it resolves the problem.
CSCvb50747 - Server and IDC login failure due to credential issue w/ IE 11 plus Win7 update KB3172605
Work around information for another Cisco product facing the same issue.
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. As you look more closely at this KB, these two Transport Layer Security (TLS) cipher suites are added to the list of ones used by IE: TLS_DHE_RSA_WITH_AES_128_CBC_SHA and TLS_DHE_RSA_WITH_AES_256_CBC_SHA.
In Firefox these can be disabled through this procedure:
1 Navigate to about:config.
2 Search for security.ssl3.dhe in that.
3 Double click on security.ssl3.dhe_rsa_aes_256_sha and security.ssl3.dhe_rsa_aes_128_sha to set them to false.
However with IE11 there is no workaround that can be done through the browser. Instead, an administrator modifies the local or domain group policy to exclude the ciphers in the SSL configuration.
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.
If the suite order is set to Disabled or Not Configured then the default order is used and block access to UCCX/Finesse. Instead, this should be set to Enabled and the cipher suite order should be modified to exclude the two ciphers mentioned above. Note the restriction that the list of ciphers are to be used, as they cannot exceed 1023 characters in length. The cipher list known to work with UCCX/Finesse 10.6 is as these:
The other option is to remove KB3161608 or KB3161606 from all machines that need to access Finesse or UCCX Web Admin.
Yup... So it's an exceptionally weak certificate that the industry is trying to mothball support for :-S.
Well, at least we know now :-)
Cheers, and thanks for taking the time to share the outcome.