Deregistering

Prev Next

The Deregistering class provides UAF logic for the entire deregistration process. It exposes two deregister methods (overloaded) for deregistering keys. To perform the deregistration, one of the two should be called.

Table: Deregistering methods and parameters lists the methods, their parameters, and the objects they return.

  Table:  Deregistering methods and parameters
PurposeParametersReturned object
Method: deregister
Deregister multiple keys based on appId and {AAID,  KeyID} tuples
  • appId: ID of the application that wants to authenticate the user.
  • authenticators: list of (AAID, KeyID) tuples to be deregistered.

Deregistration request containing data of the deregistered keys.
Method: deregister
Deregister individual keys based on appId, username, and AAID
  • appId: ID of the application that wants to authenticate the user.
  • username: the name of the authenticator's owner.
  • aaidString:aaid of the authenticators to be deregistered.
Deregistration request containing data of the deregistered keys.

Deregistering only depends on the AuthenticatorDeregistrationService that is included in the SDK. However, the service class needs to be injected with an implementation of the AssertionsManager interface to trigger the deletion of assertions when deregistering.