Please merge all the dependabot PRs and make sure that everything still works. See the PRs list.

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

In order to decommission the demo, we need to complete the following steps:

• remove references from public-facing the BC Digital Trust website (@alexgmetcalf )
• spin down the deployments (@WadeBarnes / @esune )
• remove configurations from OCP (@WadeBarnes / @esune / @rajpalc7 )
• archive this repository (@WadeBarnes / @esune )
• close this issue (@WadeBarnes / @esune )

Documentation needs to be updated to include steps on configuring the chat application along with Keycloak setup.

The services need to be migrated to OCP4, they are currently hosted in the devex-von-* namespace set in OCP3.

• the target namespace in OCP4 is 4a9599
• The contents of the folder /opt/app-root/src/data on the prod instance of dsc-chat-server will need to be migrated to the new deployment. It is just a couple of text files, so I would just copy their contents over with vim rather than setting up a PVC migrator, but see what works best for you.
• The client app uses *.vonx.io vanity URLs: please coordinate the certificate and DNS entry settings with @WadeBarnes

I think that's the best name, although open to suggestions.

This issue is a kind reminder that your repository has been inactive for 180 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Disclaimer page as the first item -- model on this https://healthbc-issuer.pathfinder.gov.bc.ca/ -- but styling to be different and I'll take a shot at the text. Nice to have is that the text be a configuration. Oh and it needs to be bilingual -- not sure if the English and French should be in the same document or two separate chunks. I suggest two titles and two chunks of text for the two languages.

No word yet on the styling for the page (colours, graphics), but assume that it will need to be English and French. Other than that, leave it plain for now.

The test and "prod" OpenVP-CANdy issuer services have been migrated to their respective ledgers now that we have a full set of CANdy ledgers and not just dev.

The migration included creating new DIDs for the services. The old DIDs and any credentials issued by those DIDs are still valid, so references to the existing credentials should be retained.

Details of the new (and old) DIDs can be found here; bcgov/essential-services-delivery#124

Affects:

• https://github.com/bcgov/issuer-kit-demo-verifier-chat/blob/main/proof-configurations/pctf-chat/test/pctf-chat.json

After the disclaimer page will be a page with a description of the service and an explanation of the data being asked of the person (first, last, province). Ideal would be on that landing page would be the QR code, but likely not possible. Note that Pierre does not have a config of keycloak setup, so either we have to have that set up for him in Docker, or the app would just use an OIDC library. In that case, perhaps the embedded QR could might be possible? Talk to @esune for best approach.

The page needs to be bilingual, so provide space in the layout for that -- either displaying both or the ability to switch between.

For now, leave plain and we'll add colours, theme and graphics later.