-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add rules for contractor credential objects #51
Conversation
WadeBarnes
commented
Sep 5, 2024
- Details can be found in Set up Traction Contractor Credential Issuers for CSB/CDT DITP#95
- Details can be found in bcgov/DITP#95 Signed-off-by: Wade Barnes <[email protected]>
<CDT DID TBD>,Cyber Security and Digital Trust | ||
<CSB DID TBD>,Court Services Branch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CDT and CSB DIDs to be defined as part of bcgov/DITP#95
@@ -0,0 +1,2 @@ | |||
author_did,schema_name,version,details | |||
<CDT DID TBD>,contractor-credential,1.0,https://github.com/bcgov/digital-trust-toolkit/blob/contractor-credential/docs/governance/employment/contractor-credential/governance.md#261-schema-definition |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the details field is free text - I forget how long it can be though.
- bcgov/DITP#95 (comment) Signed-off-by: Wade Barnes <[email protected]>
Should we create generic wildcards for |
When onboarding a new agent (team) with the endorser we have to register the agent with the endorser in one of two ways since we don't, and should never, allow open endorsement to all:
The first method is hidden and includes some manual/scripted steps. The second method is openly visible, descriptive, and has the added benefit of the history in git. My preference moving forward is to onboard teams by registering their DIDs, and then we can decide to provide them with open (wildcard) or more restricted access to write schemas and cred defs. I've purposely added some restrictions to both CDT and CSB rules. CDT, simply because this is the first time we're creating a DID for ourselves and I'd like to record our use cases as we evolve them. We have full control so it's easy for us to update our own rules. For this use case we've defined governance rules defining the rules and responsibilities of each party, the rules defined in this PR reflect those defined by the governance documentation and explicitly reflect the fact that CDT is responsible for issuing the schema and CSB is responsible for issuing the cred-def based on that schema. Adding the wild card to the version(s) allows the cred-def and schema to evolve without restriction. Further having some rules defined on our own DID (CDT) forces us to make conscious decisions about what we're using it for so we can make better decisions. |
Signed-off-by: Wade Barnes <[email protected]>