Skip to content
This repository has been archived by the owner on Sep 22, 2023. It is now read-only.

allow credential definition tagging #151

Open
burdettadam opened this issue Feb 26, 2020 · 1 comment
Open

allow credential definition tagging #151

burdettadam opened this issue Feb 26, 2020 · 1 comment

Comments

@burdettadam
Copy link
Contributor

If you create a credential definition in one agent, write it to the ledger, open up a new agent, and try to create a credential definition using the same did as in the previous agent, it will fail. Credentials definitions have tags to allow an agent to create multiple credential definitions for a single schema.

As a client, when creating a new credential definition I would be able to provide a tag that will allow me to create a new definition using the same Did and schema I have before.

@burdettadam
Copy link
Contributor Author

The aca-py agent seems to be using the schema name concatenated with underscore and version as the tag. For example S7hnXWugEPiF1x31hhQFMm:3:CL:83755:tedtested_3.3 which follows "{DID}:{MARKER}:{SIGNATURE_TYPE}:{SCHEMA_SEQ_NO}:{TAG}" pattern.

Creating multiple credential definitions in the same aca-py issuer will produce multiple credential definition listings. It is not clear if keys are being rotated by aca-py, if they are, as a client I would not expect to be able to issue credentials with the outdated credential definitions.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant