Edge external certificate - No domain name

%3CLINGO-SUB%20id%3D%22lingo-sub-1504565%22%20slang%3D%22en-US%22%3EEdge%20external%20certificate%20-%20No%20domain%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1504565%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20an%20observation%20to%20discuss.%20I%20noticed%20that%20in%20Lync%202013%20deployments%20the%20Edge%20external%20certificate%20has%20got%20the%20access%20edge%2C%20sip%2C%20webconf%20as%20well%20as%20domain%20name.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20deployed%20SFB%202019%20in%20coexistence%20mode%20with%20Lync%202013%20pool%20and%20raised%20a%20CSR%20from%20SFB%202019%20Edge%20for%20external%20cert%2C%20I%20did%20not%20see%20the%20domain%20name%20in%20it.%20Is%20this%20a%20change%20with%20SFB%202019.%20Will%20the%20certificate%20work%20just%20fine%20with%20access%20edge%2C%20sip%20and%20webconf%20FQDNs%20only.%20Appreciate%20some%20guidance%20for%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ESy%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1516248%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20external%20certificate%20-%20No%20domain%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1516248%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F172789%22%20target%3D%22_blank%22%3E%40Syed%20Azhar%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Syed%2C%20when%20you%20mention%20you%20did%20not%20see%20the%20domain%20name%20in%20it%2C%20are%20you%20referring%20to%20your%20internal%20domain%2C%20such%20as%20domain.local%3F%20Thanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-----------------%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.siplifi.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.siplifi.com%3C%2FA%3E%26nbsp%3B%7C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F685927%22%20target%3D%22_blank%22%3E%40SiplifiGroup%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1517746%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20external%20certificate%20-%20No%20domain%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1517746%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIts%20the%20routable%20SIP%20domain%20name%20(abc.com%20for%20example%20is%20my%20sip%20domain%20is%20sip.abc.com)%20in%20the%20external%20certificate.%20I%20noticed%20in%20some%20enviornments%20its%20on%20the%20external%20cert%20but%20not%20in%20some.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EAz%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1525558%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20external%20certificate%20-%20No%20domain%20name%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1525558%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F172789%22%20target%3D%22_blank%22%3E%40Syed%20Azhar%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Syed%2C%20thanks%20for%20the%20update.%20The%20domain%20name%20on%20it's%20own%20is%20not%20required%20on%20the%20certificate%2C%20you%20only%20need%20the%20service%20specific%20names%20such%20as%20sip.abc.com%20and%20webconf.abc.com%2C%20there%20is%20no%20need%20to%20just%20have%20abc.com%20specified%20on%20the%20certificate.%20I%20hope%20this%20helps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-------------------%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-ERR%3AREF-NOT-FOUND-%3CA%20href%3D%22https%3A%2F%2Fwww.siplifi.com%26nbsp%3B%7C%26nbsp%3B-ERR%3AREF-NOT-FOUND-%40SiplifiGroup%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.siplifi.com%26nbsp%3B%7C%26nbsp%3B-ERR%3AREF-NOT-FOUND-%40SiplifiGroup%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi All,

 

I have an observation to discuss. I noticed that in Lync 2013 deployments the Edge external certificate has got the access edge, sip, webconf as well as domain name.

 

I deployed SFB 2019 in coexistence mode with Lync 2013 pool and raised a CSR from SFB 2019 Edge for external cert, I did not see the domain name in it. Is this a change with SFB 2019. Will the certificate work just fine with access edge, sip and webconf FQDNs only. Appreciate some guidance for it.

 

Thanks,

Sy

3 Replies

@Syed Azhar 

 

Hi Syed, when you mention you did not see the domain name in it, are you referring to your internal domain, such as domain.local? Thanks.

 

-----------------

 

https://www.siplifi.com | @SiplifiGroup 

Hi,

 

Its the routable SIP domain name (abc.com for example is my sip domain is sip.abc.com) in the external certificate. I noticed in some enviornments its on the external cert but not in some.

 

Thanks,

Az

@Syed Azhar 

 

Hi Syed, thanks for the update. The domain name on it's own is not required on the certificate, you only need the service specific names such as sip.abc.com and webconf.abc.com, there is no need to just have abc.com specified on the certificate. I hope this helps.

 

-------------------

 

https://www.siplifi.com | @SiplifiGroup