Essential Services Delivery coordination using Digitally Verifiable Credentials.
This repository contains the build, deployment, and application configurations needed to pull a number of separate applications into a single environment and deploy them as a group of interrelated services.
The resulting services include:
Allowing Businesses and Citizen's to create "Safe Entry Points" that require the presentation and proof of a set of digitally verifiable credentials in order to authorize access.
This is an instance of bcgov/dts-esr-demo
Allowing Businesses to register as an Essential Service and in turn be able to issue Essential Service credentials to their employees.
This is an instance of bcgov/dts-safe-entry-demo
All of the Issuer Services are instances of bcgov/issuer-kit
An issuer used to obtain a digital identification credential that is used to authorize access to other services within the PoC.
An issuer used to obtain a personal health number credential that is used to authorize access to other services within the PoC.
An issuer used to obtain a business level essential services credential that is used to authorize access to other services within the PoC.
An issuer used to obtain an essential services access credential that is used to authorize access to other services within the PoC.
An issuer used to obtain a "lab result" credential that is used to authorize access to other services within the PoC.
Each Safe Entry Point is an instance of bcgov/vc-visual-verifier
Demonstrates how digitally verifiable credentials can be used to authorize access to or through a point of entry.
Demonstrates how digitally verifiable credentials can be used to provide essential services workers with authorized access to a location or facility.
This repository contains a set of openshift-developer-tools compatible OpenShift configurations
For information on how to use these configurations with the openshift-developer-tools scripts please refer to the documentation; README.md.
The application components are managed using a set of profiles.
To list the profile and their descriptions run:
Wade@hvWin10x64 MINGW64 /c/essential-services-delivery/openshift
$ ./manage -p default -e null listProfiles
Loading settings ...
Loading settings from /c/essential-services-delivery/openshift/settings.sh ...
bc - settings.bc.sh
- Safe Entry application profile
business-registration - settings.business-registration.sh
- Essential Services Registry application profile
esr1 - settings.esr1.sh
- Credential issuer profile
esr2 - settings.esr2.sh
- Credential issuer profile
healthbc - settings.healthbc.sh
- Credential issuer profile
medlab - settings.medlab.sh
- Credential issuer profile
openvp - settings.openvp.sh
- Credential issuer profile
safe-entry-c19 - settings.safe-entry-c19.sh
- Visual verifier profile
safe-entry - settings.safe-entry.sh
- Visual verifier profile
default - settings.sh
To get the details of a specific profile run:
Wade@hvWin10x64 MINGW64 /c/essential-services-delivery/openshift
$ ./manage -p healthbc -e null profileDetails
Loading settings ...
Loading settings from /c/essential-services-delivery/openshift/settings.sh ...
Loading settings from /c/essential-services-delivery/openshift/settings.healthbc.sh ...
healthbc - settings.healthbc.sh
- Credential issuer profile
- ../openshift/templates/agent/agent-build.json
- ../openshift/templates/api/api-build.json
- ../openshift/templates/db/db-build.json
- ../openshift/templates/issuer-web/issuer-web-build.json
- ../openshift/templates/issuer-web-base-image/issuer-web-base-image-build.json
- ../openshift/templates/wallet/wallet-build.json
- ../openshift/templates/agent/agent-deploy.yaml
- ../openshift/templates/api/api-deploy.json
- ../openshift/templates/db/db-deploy.json
- ../openshift/templates/issuer-web/issuer-web-deploy.json
- ../openshift/templates/wallet/wallet-deploy.json
We have moved to creating a single wallet pod across all essential services for greater resource sharing. The shared wallet is deployed from the default profile and used by all agents. Please ensure the wallet component is deployed BEFORE attempting to deploy any issuer agent
To publish or update the settings and configuration for all application profiles you can use the deployAllProfiles helper command in the manage script, for example;
Wade@hvWin10x64 MINGW64 /c/essential-services-delivery/openshift
$ ./manage -p default -e test -u deployAllProfiles
- To update all profiles in the test environment.
To publish or update a given profile or a given component within a profile you would use the genDepls.sh script. for example;
Wade@hvWin10x64 MINGW64 /c/essential-services-delivery/openshift
$ genDepls.sh -p healthbc -e test -u -c issuer-web
- To update the
issuer-webcomponent of thehealthbcprofile.
For Credential issuer and Visual verifier there are helper commands that allow you to create the scaffolding for a new profile from an existing one; createNewIssuerProfile and createNewVerifierProfile. Examples of how to use these commands can be found in the help documentation for the manage script by running;
Wade@hvWin10x64 MINGW64 /c/essential-services-delivery/openshift
$ ./manage -h
New or updated proof configurations need to be registered with the vc-authn-oidc-controller associated with the demo environment. The manage script includes a helper command to assist with this task, configureProof. Examples of how to use this command can be found in the help documentation for the manage script by running;
Wade@hvWin10x64 MINGW64 /c/essential-services-delivery/openshift
$ ./manage -h
The manage script includes a number of helper commands to help manage the environment. For a list of these commands and examples of how to use them run;
Wade@hvWin10x64 MINGW64 /c/essential-services-delivery/openshift
$ ./manage -h
To report bugs/issues/feature requests, please file an issue.
If you would like to contribute, please see our CONTRIBUTING guidelines.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.