Author Topic: SSL Certificate  (Read 5889 times)

Offline v2win

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 628
  • Country: us
  • Karma: +11/-0
    • View Profile
SSL Certificate
« on: June 23, 2009, 11:27:57 AM »
Has anyone installed an SSL certificate on any of the MSL boxes?

I am looking in the manuals and the information if pretty limited (click OK to accept the certificate) is about as much detail as it goes into.

I have a call into support but no answer as of yet.


Offline bluewhite4

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1041
  • Country: us
  • Karma: +20/-0
    • View Profile
Re: SSL Certificate
« Reply #1 on: October 14, 2010, 04:31:03 PM »
v2win,
We're looking into this for a customer, but did you ever do it or get anywhere with it?

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: SSL Certificate
« Reply #2 on: October 14, 2010, 06:58:37 PM »
v2win,
We've installed one on our AWC (internally) and one on our MBG.
Didn't have a full understanding of it when we did it so we have to buy another one for our MBG because it acts as a proxy for our UCA, mobility and AWC.

I thought we could just purchase one from godaddy but apparently not.  Just going by what our in network dude says.

Ralph

Offline Mitel100

  • Sr. Member
  • ****
  • Posts: 262
  • Country: gb
  • Karma: +6/-0
    • View Profile
Re: SSL Certificate
« Reply #3 on: October 15, 2010, 04:06:42 AM »
The SSL certificate has very limited information on MOL. However, here the process that should be followed:

1 - complete the Web Certificate with the company details and the FQDN and select generate certificate
2 - copy and paste the text that is generated into notepad.
3 - send this to a CA to get a signed certificate
4 - import the signed certificate back into the MSL

However, for the MBG and AWC, there is an extra step to consider, as the MBG can act as a proxy and the AWC has two FQDN's, then when making the request to the CA, you need to add a 'Subject Alternate Name' with all the FQDN's the proxy will handle and for the AWC the second FQDN.

I hope this help.


 

Sitemap 1 2 3 4 5 6 7 8 9 10