Manage devices

This guide will walk you through the process of managing devices for a regular user. You need to have an appropriate role to manage users. A device can be a mobile phone, tablet or smart watch that runs (mobile) apps on Android or iOS.

What is required?

To successfully complete this topic guide you need to ensure that the following prerequisites are met:

  • Onegini UMA instance must to be running, for the sake of this guide we assume it's available on https://uma.example.com
  • Onegini CIM instance must to be running, for the sake of this guide we assume it's available on https://idp.example.com
  • Onegini Token Server instance must to be running, for the sake of this guide we assume it's available on https://tokenserver.example.com
  • The Person API and configuration API must be enabled in the Onegini CIM instance
  • Credentials for the end user API must be configured in the Onegini Token Server. The credentials in this guide will be end_user_api_user and end_user_api_password.
  • The user must have successfully registered in the (mobile) app with their account.

Configuration

Make sure that the connection to the Onegini CIM Person API, Configuration API and the Onegini Token Server end user and events API are properly setup. See the API connection for further details.

Managing devices

Devices are shown in the user's profile. For example, to manage the devices of Joe Doe with email address joe.doe@example.com you need to:

  1. Log in to Onegini UMA as a user with user management role enabled.
  2. Find the user with email joe.doe@example.com

The following information is shown when a user has registered devices:

Table of mobile devices

  • Last used: shows when the user has last used the app on this device
  • Application name: name of the (mobile) app
  • Platform: android or ios
  • Device name: a name the user has given to their device
  • Mobile authentication: login or approve transactions on the website using the (mobile) app. This is optional and there are two options when the user can do mobile authentication:
    • Activated: the website needs to instruct the user to open the app and complete the login or approval.
    • Activated and can receive push notifications: a push notification is sent to the device to login or approve a transaction. The app is opened when the user clicks on the notification.

The 'Latest Events' section contains recent events captured by both the Onegini CIM and the Onegini Token Server.

Delete devices

This can be useful when the user has no longer access to the device. A delete button is shown for every device. When the user wants to use the device again, they need to follow the registration process of the (mobile) app.