04-18-2019 09:41 PM
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
05-13-2019 03:23 AM
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?
Thanks !
05-16-2019 08:19 AM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide