The Onegini Mobile Security Platform is a flexible platform that connects with authenticators of all brands as well as identity providers that are currently on the market.
The out of the box integration of Samsung SDS FIDO solution with the Onegini MSP will offer greater ease and more security for customers using Samsung Galaxy devices, iOS devices as well as other selected OEMs. When you use MSP 3.0, the Samsung SDS FIDO solution will be plug and play. The product is built based on FIDO specifications which is the de facto standard for simpler and stronger biometric authentication technology. While you can still use the authenticators already provided by MSP, users with a Samsung SDS FIDO server can use any FIDO enabled authenticators on the market. So for all existing Onegini and Samsung SDS FIDO customers this is a win-win improvement.
For devops we added a one line installation script. It takes core of our setup with dockers.
We've completely redesigned our mobile SDK's. First of all we've reduced the amount of methods you have to implement, so it will take you less time to get started. Take error handling for instance, our previous solution was strongly based on handlers. We were creating additional handlers for every error that could occur. This resulted in you having to implement every method while not every developer needed to handle every error differently. We've also separated the concerns more clearly making it all easier to understand and flexible.
The new API comes with a new SDK configurator. The tool was created to help developers setup their apps to use the Onegini Mobile SDKs easily. With just 1 command, you can (re)-generate config models, setting up the url of the token server and certificate pinning.
We've completely redesigned the token server UI. Let's give you a short overview of the changes:
Less menu items and a clearer devision into topics. All configuration is moved to the configuration tab. Here you can set app versions, setup push authentication or configure your pin policies and IDP. Under activity you can browse through all the events in the system. In the users and app installations tabs you can force a user to enrol again or troubleshoot issues for a specific device.
In the first tab we added a lot of insightful information, so you can more easily make security related decisions. Onegini is not yet another statistics platform, but we will give you a clear high level overview of the users enrolled and how active your users are. Verify login success vs failure for authenticators like Pincode versus Fingerprint. Thanks to insights into mobile OS versions, you can more easily decide to force a small percentage of users to upgrade their devices.
There should be clear separation between the token server core and the parts that you customise. Templates and custom plugins are now stored in the database. Therefore you can now import and export messages and templates from within the new admin panel, making it easier for you to manage while providing you with an easier path for upgrading. Under the hood we've updated the token server to springboot.
There are many examples of users who want to keep finances completely separated. You could want a user account for yourself, a shared account for you and your partner, for you and your business etc. That's why the MSP now enables multiple users sharing the same device without having to perform enrolment again. You and your partner are now able to enrol for push authentication on the same device. The Mobile Security Platform will discover whether a mobile device is used by multiple people and by how many people it is being used. As a developer you'll only have to implement the views in your app for switching between profiles. The Android and iOS SDK provide a profile specific storage, showing a list of registered profiles, which you can update and delete.
We've added a version compatibility matrix with an overview of the versions out there.
You'll also find information helping you decide if you should start with version 3.0 or stick with the stable release MSP 1.5. Still unclear? Don't hesitate to reach out to us! firstname.lastname@example.org