IMPORTANTE: Caducidad de certificados en la versión 4x de mSuite

Tuesday 13th October, 2009
AVISO IMPORTANTE:

Para los que todavía estéis usando la versión 4x de mSuite. El 19 de Noviembre caducan las firmas digitales que vienen con mSuite 4:


Server: Personal Certificate (CommonTimeEval2009.pfx) - Expiry date: November 19th, 2009
Mobile device: Root Certificate (CommonTimeCA.cer) - Expiry date: November 19th, 2009


Tenéis que bajar los nuevos certificados (mSuite4CA.cer y mSuite4.pfx) desde la web de Commontime y bajarlos a las carpetas donde tenéis mSuite instalado que por defecto suele ser:   C:\Program Files\CommonTime\mSuite.

URL de descarga:
http://hosting.commontime.com/downloads/certificate/mSuite4.zip

Para instalar la firma digital en los dispositivos (antes de instalarla en el servidor), podéis crear un nuevo paquete de instalación para los usuarios o estos utilizando su navegador de Intermnet en el dispositivo se la pueden bajar desde:
Symbian: http://symbiancert.commontime.com
Windows Mobile: http://wmcert.commontime.com

Aquí tenéis las instrucciones en Inglés de como instalar el certificado en el servidor mSuite:
You will need to install and activate the new server certificate before it expires on November 19th, 2009.  All mobile devices must have the new root certificate already installed (see Step 2 above).
a.        Go to the All Servers view
b.        Double click on the server that runs the Connection Management Service (CMS)
c.        Go to the Connection Management tab and run the first of the two wizards on that page (the one to the right of Default CMS Template)
d.        On the General Settings page, click the Add certificate button (below the Certificates panel).
e.        Browse to the mSuite4.pfx certificate, select it and click Open.
f.        Enter the password which is Commontime (it is case sensitive!) and click OK.
g.        In the Certificate panel, select mSuite4.

If mSuite4 does not appear in the Certificate panel or, when you select it, you see the warning message ** The Selected certificate does not exist in server…**, repeat steps d, e. and f above.

Image:IMPORTANTE: Caducidad de certificados en la versión 4x de mSuite

 


h.        Click Next to the end of the wizard and then click Finish.  Finally, go to Monitoring > Status > [servername] and right click on Connection Manager Server and click Restart.

The new server certificate is now active and you can verify this by checking the configuration information printed at startup in the CMS log.  To do this, go the CdzConnMgr subfolder of the mSuite program folder and open the log file for today.  You should see log lines similar to these:

2009-10-03 08:36:57 info   app :   mCenter database is v2.8
2009-10-03 08:36:57 trace app :  connection manager configuration:
2009-10-03 08:36:57 trace app :   ip address       = *
2009-10-03 08:36:57 trace app :   port               = 605
2009-10-03 08:36:57 trace app :   session-expiry  = 5
2009-10-03 08:36:57 trace app :   certificate       = mSuite4
2009-10-03 08:36:57 trace app :   suites             = aes-128, aes-192, aes-256, aes-128 (k) 2009-10-03 08:36:57 trace app :   mnotes-servers = MYSERVER  
2009-10-03 08:36:57 trace app :   cap-servers      MYSERVER
2009-10-03 08:36:57 trace app :   auth-servers     = MYSERVER
2009-10-03 08:36:57 trace app :   chat-servers     = MYSERVER

In particular, the ‘certificate’ should now show as “mSuite4”.


Comments [0]

Posted in: at 13:13:00
Location: Derby, Gran Bretaña.