Same issue as was referenced in IIWBook @esune.

email-verification services should be deployed in test, prod.

• test services are all-new and will need to be configured from scratch.
• prod services should have their wallets carried over from the devex-von-image-tools namespace so we can decommission the old ones. @wadeking98 please proceed with deploying the agent in read only mode, using the wallet and secret values from OCP3. Once ready, coordinate with @WadeBarnes to add the vonx.io routes and certificates, and switch the DNS entry to point to the new cluster.

PM from ngrok here. I'm opening this issue to let you know what ngrok has recently started requiring a free account and authtoken to start the agent. It looks like your software might already work with an authtoken, but there might be users or integrations or docs that need to updated.

Please reach out to [email protected] if you are having any issues.

Thanks again for using ngrok!

I've copied the original notice posted to twitter below:

As a part of our ongoing efforts to make ngrok more secure, starting on December 19, 2023, all usage of ngrok will require an account on either our free or paid tiers. 

To connect to the ngrok service via the agent, SDK, or ingress controller, you must add a valid authtoken that is linked to an active free or paid account. Any new or existing connections without a valid authtoken will result in error code 4018.

Learn more here: https://ngrok.com/docs/errors/err_ngrok_4018/

Deploy a new demo app to test vc-authn authentication using a Verified Email credential, now that the CSB Audio demo uses a different credential.

I assume it's just a search and replace, but I don't have a local test environment setup.

For example, so we can use the email verifier with our issuer kit (which issues against BCovrin test)

This issue is a kind reminder that your repository has been inactive for 181 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!

Running in an Ubuntu VM (18.04/20.04 -->tried both)

Following basic steps in this demo app:

1. script to start ngrok for agent tunnel
2. manager build and then manage up

Getting the following error for the agent container:

When running with aca-py agent: ghcr.io/hyperledger/aries-cloudagent-python:py3.6-indy-1.16.0-0.8.0

the agent has no problem, and I can pull up the swagger api http://0.0.0.0:5000/api/doc#/

With both agents, the django app sending requests to that api does not run, see logs :
(container docker_email-verifier-service_1 is outputting the same for localhost:8080)

Getting the below error while creating genesis transaction for email-verifier-agent:

File "/home/indy/src/aries-cloudagent/aries_cloudagent/ledger/indy.py", line 220, in _submit
email-verifier-agent_1 | f"Ledger rejected transaction request: {request_result['reason']}"
email-verifier-agent_1 | aries_cloudagent.ledger.error.LedgerTransactionError: Ledger rejected transaction request: client request invalid: UnauthorizedClientRequest('The action is forbidden',)

@wadeking98 -- please update the dependencies and verify the app is still functioning.

At email verification service page, submitting the email is failing with the below error :

If I should be able to do this myself, please let me know how.

Thanks!

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.

Getting the listed error while trying to bring up the indy-email-verification service

steps to reproduce

Terminal 1 :

    cd indy-email-verification/
    ./start-ngrok.sh

Terminal 2 :

    cd indy-email-verification/docker/
    ./manage down
    ./manage build
    ./manage start

machine details

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!

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 :)

Update genesis config map in https://github.com/bcgov/indy-email-verification/blob/master/openshift/templates/email-verification-agent/email-verification-agent-deploy.yaml to point to http://test.bcovrin.vonx.io/

This issue is a kind reminder that your repository has been inactive for 187 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!