New Claim Definition & Edit Existing Claim Definition

[andrewBSTan]

After managing to setup the environment and run the examples as it is, I am exploring how one can edit the claims definition or create new ones. Although I have edited the Schemas.json in the relevant directory delete the existing images and rebuild them, the revised claim definition do not seem to be recognizing the additional attribute added.

Is there any reload that I need to perform?

Thanks.

[jolapin]

Hello Andrew,

I had the same issue. I was not able to succeed defining a new one but in order for your modifications of an existing one to be accepted you need to rebuild
It's maybe overkill but it worked for me.
Best regards

[sunburntcat]

I too am trying to deploy new schemas. I found this repo yesterday, so it might be helpful to you guys as well: https://github.com/hyperledger/indy-sdk/tree/master/doc/how-tos/save-schema-and-cred-def/python

They have a java walkthrough as well ( save-schema-and-cred-def/java ).

[brycecurtis]

The schemas are located in permitify/site_templates//schemas.json. In order for a new schema to be used, you either need to wipe out the ledger or bump the schema version number.
You also need to edit the config.toml file, which maps the input field from the generated form to the schema attribute.

If you changed the schema version, then to use this new schema in a proof, all proof_request.json files need to be updated to reflect the new schema version.

Once changes are made, it's best to delete the docker containers and images, and rebuild. Make sure you clear your browser cache as well.

The way that Permitify is written, you can only have one schema per issuer. This is why there are acme_corp and an acme_corp_apply issuers. Adding a new issuer is quite involved. It requires editing docker compose files, manage scripts, and a file or two under TheOrgBook directory.

[sunburntcat]

@brycecurtis Appreciate the response. Would the nonce need to be updated within the proof_requst.json? Looks like its value is the same across all current issuers.

[brycecurtis]

@sunburntcat The nonce should be unique for each request, but for a demo environment it's kept the same to make it easy.