Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Key/Backend paring config #106

Open
jevonearth opened this issue Aug 6, 2020 · 0 comments
Open

Key/Backend paring config #106

jevonearth opened this issue Aug 6, 2020 · 0 comments
Assignees
Labels
icebox Low priority or unknown demand

Comments

@jevonearth
Copy link
Contributor

jevonearth commented Aug 6, 2020

Problem Statment

If a signatory config has multiple backends setup, that contains the secret for an address, it is not possible to specify which backend or backends should be used, and (if more than one) in what order.

User Story:

As a signatory operator with multiple vaults configured in my signatory.yaml file, I want to set preference on an address in the signatory config so that it will only use specified backends for signing.

If I have an address such as tz3MhmeqpudUqEX8PYTbNDF3CVcnnjNQoo8N and I know that the private key for this address is only in backend yubi_abc I want to "pin" my configuration so that signatory only uses that backend and no others.

@Innkst Innkst added this to the v1.0 milestone Nov 16, 2020
@jevonearth jevonearth added the icebox Low priority or unknown demand label Jun 8, 2022
@jevonearth jevonearth removed this from the v1.0 milestone Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
icebox Low priority or unknown demand
Projects
Status: No status
Development

No branches or pull requests

3 participants