[cisco-voip] Renewing web certificate? (FQDN)

[Lelio Fulgenzi]

I ran into something similar. I think. 

When I created a self-signed cert it only had the host name. 

After I added DNS capabilities and added the domain, users complained about the cert warning. 

I had to regenerate the self-signed cert in order to remove that error. 

So, I'm thinking, do you have the domain configured for the server? 

I'm on v7.1 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Jonathan Madziarczyk" <jmad at cityofevanston.org> 
To: cisco-voip at puck.nether.net 
Sent: Monday, January 30, 2012 12:38:58 PM 
Subject: [cisco-voip] Renewing web certificate? (FQDN) 




My tomcat cert has expired this past week and I’m trying to renew it to cut down the chatter on the web interface for end users. 



The problem I’m running into is that the old cert apparently used the FQDN. This year, when I try to regenerate the request it looks like it’s only using the host name and not the FQDN. 



Any ideas on how to get a valid cert request with the FQDN from CUCM (6.1) that I can run through my Microsoft CertServ? 



Jon 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120130/e72617ee/attachment.html>