I’m working with a customer who has run into a known bug (CSCuj95347) that prevents the Finesse Server from authenticating to the AWDB using NTLMv2. The workaround is to disable NTLMv2 within the Local Security Policy on the AW for both the Client and Server settings, which has resolved the issue. However, the Windows Security engineer discovered that the packets in this traffic appear to have the “No encryption” flag enabled. This is a concern for PCI compliance and a possible show stopper.
A) The customer would like to know if there is a way to encrypt this traffic?
B) This bug is resolved in Finesse 10.0(1), but is the “No encryption” flag enabled is this version as well?
The Finesse JDBC driver is configured to use NTLM. Make sure the AWDB is also configured to use NTLM. Note Finesse does not support NTLMv2. If the AWDB is configured to use NTLMv2,Finesse cannot connect to the AWDB
Hopefully this bug will be resolved, but it's worth pointing out that PCI only demands encryption over the wire on untrusted networks like the internet. Since Finesse and AW are typically co-located on a private trusted network, PCI should not be an issue.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...