is the engineering special resolving this issue released?
its the same issue on cucm. i had to convert all my certificates to single name and that was a pain
Hi, I raise a case referring to this bug, asking if there is an ES.
However, how did you convert your cert to single name? Does it mean that you didn't select MultiSAN, but did instead separate tomcat certs for each hosts?
If it can helps, I generate CSR on both Unity of the clsuter, but not in MultiSAN, and removing the parent domain (because it's a SAN).
Insert then the certs and issue is solved, so basically this is the Workaround 1 referenced on the bugID.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: