Skip to content

TUI - manage key aliases - process improvements

To improve an onboarding process and managing key aliases, clive will request node for an available public keys for working account added to the profile. The flow is as follows:

  1. A user adds a working account to the profile.
  2. Clive asks node for an available list of public keys for the working account.
  3. Clive asks beekeeper if beekeeper has a private keys for the public keys.
  4. A user will see the list of available aliases connected to the working account.
  5. There is no automatic synchronization, a user has to choose the keys to be used.

To allow the above flow, the following changes should be done:

I. TUI- views

  1. Configuration

image

a. Change Manage authority to Manage key aliases.

  1. Authorities

image

a. Change Authorities to Key aliases
b. Change Authority name to Aliases
c. Change Authority Type to Public Key
d. Change New authority (bottom menu) to New alias
e. After clicking Edit, a new view is shown that allows to edit an alias.
f. Additionally it should be possible to save a new alias (it is possible to have two aliases for the same public key) on the Edit view.
g. If there is no private key for the alias in the beekeeper, there should be an option to import one.
h. The alias name should be unique.

  1. Edit authority

image

a. Change Edit authority to Edit alias.
b. See point 2.f. - it should be possible to save the same key with different alias.

  1. The view Define key - no changes.

II. TUI Onboarding process - changes

  1. After a user enters a account name (view Set name), there should be added two requests:
  • Clive asks node for an available list of public keys for the working account.
  • Clive asks beekeeper if beekeeper has a private keys for the public keys.
  1. Clive shows the view key aliases.
  2. The view Define keys should be removed from onboarding process.