---
title: Managing registered devices
description: PingOne Advanced Identity Cloud PingAM Android iOS JavaScript
component: orchsdks
page_id: orchsdks:journey:use-cases/device-self-service/index
canonical_url: https://developer.pingidentity.com/orchsdks/journey/use-cases/device-self-service/index.html
revdate: Wed, 17 May 2023 14:10:20 +0100
keywords: ["PingOne Advanced Identity Cloud", "PingAM", "Journeys", "Setup & Configuration", "Source Code", "Use Case", "SDK"]
section_ids:
  get_started: Get Started
---

# Managing registered devices

[icon: circle-check, set=far]PingOne Advanced Identity Cloud [icon: circle-check, set=far]PingAM [icon: android, set=fab]Android [icon: apple, set=fab]iOS [icon: js, set=fab]JavaScript

PingOne Advanced Identity Cloud and PingAM support registration of many different authenticator device types to support your multi-factor authentication journeys:

* WebAuthn/FIDO authenticators

  The registered device acts as an *authenticator* and uses public-key cryptography to securely sign an assertion from the server.

  Register WebAuthn devices using the [WebAuthn Registration node](https://docs.pingidentity.com/auth-node-ref/latest/webauthn-registration.html).

  To learn more about implementation, refer to [Integrating with FIDO (WebAuthn) auth journeys](../fido/index.html).

* Device binding

  The registered device generates a key pair and a key ID. The Orchestration SDKs send the *public* key and key ID to PingOne Advanced Identity Cloud or PingAM for storage in the user's profile.

  Bind devices using the [Device Binding node](https://docs.pingidentity.com/auth-node-ref/latest/device-binding.html).

  To learn more about implementation, refer to [Introducing Device Binding](../device-binding/index.html).

* Device profiling

  The Orchestration SDKs collect specific data about the registered device to create a profile that helps to identify it during authentication journeys.

  Profile devices using the [Device Profile Collector node](https://docs.pingidentity.com/auth-node-ref/latest/device-profile-collector.html).

  To learn more about implementation, refer to [Introducing Device Profiling](../device-profiling/index.html).

* OATH MFA devices

  The registered device generates a one-time passcode that your users enter into the authentication journey.

  Register OATH devices using the [OATH Registration node](https://docs.pingidentity.com/auth-node-ref/latest/oath-registration.html).

* PUSH MFA devices

  The registered device receives a PUSH notification from the server that the user must approve to continue their authentication journey.

  Register PUSH devices using the [Push Registration node](https://docs.pingidentity.com/auth-node-ref/latest/push-registration.html).

You can use the Orchestration SDKs to enable users to manage the devices and authenticators registered to their accounts. For example, they can list, rename, and delete their devices.

## Get Started

[icon: android, set=fab, size=3x]

#### [Android](android-device-self-service.html)

Device self-service in Android apps

[icon: apple, set=fab, size=3x]

#### [iOS](ios-device-self-service.html)

Device self-service in iOS apps

[icon: apple, set=fab, size=3x]

#### [JavaScript](javascript-device-self-service.html)

Device self-service in JavaScript apps