The table below shows the version compatibilities of all major releases for MSP + CIM.
|Connect Version||Status||Released||MSP Version||CIM Version|
|4.0 Broccoli||Maintenance||March 2018||MSP 4.0||CIM 3.2|
|3.1 Carrot||June 2017||MSP 3.1||CIM 3.1|
The table below shows the version compatibilities of all major releases of the Mobile Security Platform (MSP). The table only shows publicly released versions.
|MSP Version||Status||Released||Token Server Version||iOS SDK Version||Android SDK Version||Security Proxy||Statistics Engine||Extension Engine||Cordova Plugin||SDK Configurator||iOS Example app||Android Example app||Cordova Example app|
|MSP 4.1||Latest||February 2018||Token server 7.x||...||...||...||...||...||...||...||...||...||...|
|MSP 4.0||Maintenance||November 2017||Token server 6.x||iOS SDK 7.x||Android SDK 8.x||Security Proxy 3.x||Statistics Engine 1.x||Extension Engine 1.x||Cordova Plugin 4.x||SDK Configurator 4.x||iOS example app 4.x||Android example app 4.x||Cordova example app 4.x|
|MSP 3.1||June 2017||Token server 5.x||iOS SDK 6.x||Android SDK 7.x||Security Proxy 2.x||Statistics Engine 1.x||Extension Engine 0.x (Alpha)||Cordova Plugin 3.x||SDK Configurator 4.x||iOS example app 3.x||Android example app 3.x||Cordova example app 3.x|
|MSP 3.0||Planning EOL||September 2016||Token server 4.x||iOS SDK 5.x||Android SDK 6.x||Security Proxy 1.x||Statistics Engine 1.x||N/A||Cordova Plugin 2.x||SDK Configurator 4.x||iOS example app 2.x||Android example app 2.x||Cordova Example App 2.x|
|MSP 1.5||EOL||September 2015||Token server 3.x||iOS SDK 4.x||Android SDK 5.x||Security Proxy 1.x||N/A||N/A||
Cordova plugin 1.8.x
Cordova native screens 1.8.x
|SDK Configurator 2.0.x||N/A||N/A||N/A|
|MSP 1.0||EOL||July 2013||Token server 2.04.x||iOS SDK 2.04.x||Android SDK 2.04.x||Security Proxy 1.x||N/A||N/A||N/A||N/A||N/A||N/A||N/A|
|MSP 0.9||EOL||Jan 2012||Token server 2.02.x - 2.03.x||iOS SDK 2.02.x||Android SDK 2.02.x||N/A||N/A||N/A||N/A||N/A||N/A||N/A||N/A|
Note that you may need to scroll horizontally to see the whole table.
The table below shows the version compatibilities of all major releases for Consumer Identity Management.
|CIM Version||Status||Released||IDP Version||UMA Version|
|CIM 3.2||Maintenance||December 2017||IDP 3.2x||UMA 1.1x.x|
|CIM 3.1||Planning EOL||April 2017||N/A||N/A|
|CIM 3.0||EOL||September 2016||IDP 3.10.xx||UMA 1.08.xx|
|CIM 2.0||EOL||August 2016||IDP 2.xx||UMA 1.08.xx|
Onegini uses semantic versioning for all software products. Given a version number major.minor.patch:
Most customers want to stay secure and have the least effort between releases. If you're like most, just follow the release marked with Stable / Maintenance release release marked in the Component Release Matrix. This means planning for a major upgrade once a year and patch updates during the year. If your project starts now and will take a month or two before going live, you could choose to go with the latest release, specifically if you need certain features.
In addition Onegini provides roughly 4 minor releases a year. From a security standpoint, there's no need to upgrade right away. If you like or require features from such a release, go for it. Naturally you can choose a different strategy. Please contact our consultants for tailored advice.
Onegini provides roughly 10 security updates a year. For maximum security we advise you to update soon after a patch update. We'll pro-actively inform you when we strongly advise to update in all cases.
Moreover: The MSP is a security product that is built for the enterprise. We understand updating is not always easy in your organization, so we've tried to make it as straightforward as possible. Onegini carefully automated all tests and functionality on all levels, so don't expect issues when updating a patch version.
Even-though the MSP doesn't fully rely on the client side for security, we advise you to update your apps in similar fashion to the server components: One time a year a major update and roughly 10 times a year for a patch.
When a platform version is marked as a latest release, all unit testing and functional testing will be done, but the full platform may not yet be supported and API's may still change. So extra effort to upgrade may be required later on. Please contact our consultancy department for a tailored advise.
Always plan an upgrade within a year to qualify for long term support if the release was not marked stable / maintenance yet.