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

Determine how to standardize external entity statements vs internally provided entity statements #24

Open
rs59 opened this issue Feb 4, 2025 · 0 comments

Comments

@rs59
Copy link
Collaborator

rs59 commented Feb 4, 2025

Consider:

  • Decoding external entity statements to provide them internally (stored as Entity Statement) in the database (advantages: easier to make a flexible data format, it is also unlikely that the internal DB contents will be changed without first having the external ES changed first; disadvantages: less rigorous checks on data format, potential mismatch between internal and external entity statements). Might want to run a DB integrity check on startup or an ES validator if sent by issuers and/or have a view on the DB which can be used to visualize all contents.
  • Encoding database columns to provide them externally (advantages: easier visualization of data; disadvantages: hardcoded format in database can make it harder to upgrade DB, slower)

Middle ground:

  • Store signatures in DB and run pre-check to confirm signature accuracy; store JWKs as a string to avoid specific keys being used; run DB pre-check
@alexfigtree alexfigtree moved this to Issuer Registry Backlog in DCC Engineering Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Issuer Registry Backlog
Development

No branches or pull requests

1 participant