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.

Sign up for GitHub

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

Jump to bottom

Feat: Add JWT support on the Signatory API #341

Closed
jevonearth opened this issue Mar 30, 2023 · 0 comments
Closed

Feat: Add JWT support on the Signatory API #341

jevonearth opened this issue Mar 30, 2023 · 0 comments
Assignees
@AbineshECAD

Comments

@jevonearth
Copy link
Contributor

jevonearth commented Mar 30, 2023 •
edited by AbineshECAD
Loading

Trili requires Signatory API authorization. Instead of using the "authorized_keys" scheme from Octez, we will implement standard JWT authentication. Initially, keys will be stored in the Signatory YAML config, with the possibility of adding KMS storage later if requested.

Key features:

  • Operators can configure multiple keys for individual end users.
  • Optional key expiry for easier rotation.
  • Operators can bind specific keys to specific PKHs in the configuration.

Related issues; #246, #199, #351, #352
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AbineshECAD AbineshECAD

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jevonearth @stephengaudet @AbineshECAD