MiCollab Client Mobile deployment

[johnp]

I would test via a SSL testing site. You need the keyfile for this cert and it needs to be in RSA format

[Gasmanz]

Are you still on version 7.0?

Yes, it is part of the MiVoice Business Express

Most of our customers are on MiVB Express too. Its quite easy to backup the entire config, deploy a new instance on 7.1 and restore the config. 7.1 is a lot more stable with less bugs.

[acejavelin]

Are you still on version 7.0?

Yes, it is part of the MiVoice Business Express

Most of our customers are on MiVB Express too. Its quite easy to backup the entire config, deploy a new instance on 7.1 and restore the config. 7.1 is a lot more stable with less bugs.

This is my first and only MiVB Express, never upgraded one before. I'll look into it this week.

Sent from my MotoG3 using Tapatalk

[acejavelin]

I would test via a SSL testing site. You need the keyfile for this cert and it needs to be in RSA format

I ran an SSL Server test from Qualys SSL Labs (https://dev.ssllabs.com/index.html) and DigiCert's SSL Certificate Checker (https://www.digicert.com/help/) and although it got an F rating for a vulnerability (OpenSSL Padding Oracle vulnerability (CVE-2016-2107) , the certificate portion passed with no issues from both sites.

Is that what you mean?

[johnp]

Yes, never had and F mostly B. I am trying to remember what the fix was for a customer who had the same message.

[martyn]

Did you end up figuring this one out? Experiencing the same issue with the cert having been loaded, but still being returned an error of Error: DEPTH_ZERO_SELF_SIGNED_CERT when running the diagnostics.

[acejavelin]

Did you end up figuring this one out? Experiencing the same issue with the cert having been loaded, but still being returned an error of Error: DEPTH_ZERO_SELF_SIGNED_CERT when running the diagnostics.

No... we were dealing with other issues and they are scheduled for an upgrade to the new MiVBX release towards the end of the month, we tabled it until the upgrade was complete.

[martyn]

I figured my issue out as being that the intermediate cert did not also contain the root, which is why the deployment service was then failing. Through a bit of trial and error I figured this out, and then once I had combined the two and uploaded it as the intermediate along with the signed then everything kicked in to life.