This document provides a basic overview of how Mumba can link to external applications through the use of our ‘pop out’ tiles on the user’s dashboard. Mumba has two ways of launching external apps including:
Popping open an external web-app in a browser
Popping open an external mobile app on a tablet/phone device
To achieve the best possible experience when popping out to different systems, we recommend using a Single Sign-on approach so that users don’t need to login to these systems once they’ve clicked the tiles in Mumba.
Single sign-on is an authentication process that allows the user to access multiple applications without needing to enter in their user credentials repeatedly. Once they have logged into Mumba, any application using the same authentication process will be automatically logged into as well.
In order to achieve SSO, you need to have a central authentication system set up within your business (e.g. Active Directory, SAML, ADFS etc) that all other systems that require single sign-on (such as Kronos, Preceda, Sharepoint etc) are connected to.
Mumba will then connect and authenticate against this central service provider and will then share the login with the other systems that have also been connected. This is something that needs to be setup internally by your IT department. Mumba will then need to be provided with a link that will launch the third-party app connected to the same identity provider.
If this has been set up on your end, then once an employee logs into Mumba and clicks on the link provided, it will launch in a new web browser and they will automatically be logged into the target system.
A web-app is an app that can be accessed via the web through a browser (i.e. a website).
In order to create the pop out, Mumba will include a tile on the user’s dashboard that contains a URL link to the external web-app (you need to provide us with the URL link).
On the desktop version of Mumba, the target web-app will launch in a new web browser tab.
On the user’s mobile device, the link will launch the web-app in a mobile browser.
If the target web-app is using the same SSO identity provider as Mumba, then SSO will be achieved and the user will be automatically logged into the web-app.
If the target web-app is not using the same SSO identify provider (or is not connected to any SSO service) then the user will be directed to the target web-app’s login page and the user will need to enter in their login credentials for that particular system.
A mobile app is an app that is downloaded and installed on an Android or iPhone tablet or phone.
When one mobile app switches to another app, this is known as ‘context switching’ or ‘invoking’ another app. Context switching requires us to know a special ID of the target app and will often require some testing to perfect. We therefore need to work with the relevant app vendor to achieve this process.
Once Mumba has successfully implemented the app context switching, when a user clicks on the tile the target app will appear, if it exists on the users device. If the app does not exist then the user will be taken to the app store to download the target app.
There are often complexities in switching between two mobile apps that may inhibit the SSO process hence we look at each scenario on a case by case basis.
Please note that switching to another mobile app is a complex situation and requires special project scoping hence this feature is only available if it is defined in your Mumba license and/or consulting agreement.