Managing Phones for a User Identity
Learn how to manage the phones associated with a user identity.
Last updated
Was this helpful?
Learn how to manage the phones associated with a user identity.
Last updated
Was this helpful?
An app user may have several phones. When they sign into their account on your mobile application, it is important that additional phones also provide access. Seam facilitates this access by registering each phone within the and synchronizing across these phones. Further, Seam provides a feature to deactivate a phone if an app user loses it.
When an app user signs in to a new phone, Seam can automatically set up the new phone, generate matching credentials, and issue these credentials. To facilitate this capability, you must when creating a mobile credential.
If an app user loses their phone or wants to deactivate it, you can deactivate the phone. Seam then automatically invalidates the stored credentials on their deactivated phone.
Command:
Output:
Command:
Output:
Command:
Output:
To a phone, provide the ID of the phone. When a phone is deactivated, Seam also revokes all the credentials issued to the deactivated phone. Seam also removes the associated ACS credentials from the ACS.
To retrieve the list of phones that the mobile app user has used to sign in to their account, use the endpoint and include the ID of the user identity.
To retrieve a phone by its ID, use the endpoint and include the device_id
of the phone.