Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Product

Full PreVeil, iOS app, and Android app

Common Causes

  • A recovery group is not assigned to a user in an organization or an individual

  • Multi-tenancy is in effect

  • An approval group was not properly applied as a recovery group

Recovery Group unassigned

A recovery group must be assigned prior to performing an account recovery, and the underlying process must be completed. The assignee and members of the recovery group must be online in a two-week period to complete the assignment.

Multi-tenancy

An account recovery may have been successful, but the account inaccessible owing to multi-tenancy. Subsequent attempts to recover can result in the error message. The solutions are two reset the tenant or to disable multi-tenancy.

Note: it is advised to retain multi-tenancy on a shared computer.

Improper application of Recovery Group

To set up a Recovery Group, the assignee’s private key is broken into fragments or shards, with each shard assigned to a member of the group. These shards are encrypted and kept on the server. When a user needs to recover their account, each of the required approvers retrieves their encrypted shard from the server, decrypts it using the approver’s private key, and sends the decrypted shard securely to the user that is recovering.

It is important that the assignee and members of the group are online with PreVeil software running properly for the process to complete. The process happens automatically when users are online, and no actions are required on their part. If users are not online or have properly running software, within a two-week period, then the recovery group application will fail as timeframe to complete key fragmentation will have expired.

  • No labels