Problem with local dev config for demo issuer front-end about oid4vc-demo HOT 4 OPEN

I notice the docker .env file has sphereon2023: https://github.com/Sphereon-Opensource/OID4VC-demo/blob/develop/docker/.env.oid4vci-demo-frontend#L2

from oid4vc-demo.

To use ngrok to tunnel to my locally running agent, I also had to change the credential_issuer and credential_endpoint in packages/agent/conf/dev/oid4vci_metadata/sphereon.json:

It would be nice if the agent endpoint could be configured purely through env vars.

Does the correlationId need to be a URL or can it be a URI that's not tied to the actual deployment address?

from oid4vc-demo.

Through experimentation with the public demo issuer at https://ssi.sphereon.com/demo/issuer/#/credentials/verify/request, I see it uses the sphereonWallet definition ID (not sphereon or sphereon2023). Running the demo issuer locally, if I change packages/oid4vci-demo-frontend/.env.local to have:

REACT_APP_OID4VP_AGENT_BASE_URL=https://ssi.sphereon.com/agent
REACT_APP_OID4VP_PRESENTATION_DEF_ID=sphereonWallet
REACT_APP_OID4VCI_AGENT_BASE_URL=https://ssi.sphereon.com/sphereon2023
REACT_APP_ENVIRONMENT=sphereon
PORT=5001

then the fetched auth request includes the correct claims > vp_token > presentation_definition for the identity challenge:

...
  "claims": {
    "vp_token": {
      "presentation_definition": {
        "id": "sphereonWallet",
        "purpose": "You need to prove your Wallet Identity data",
        "submission_requirements": [
          {
            "name": "Sphereon Wallet Identity",
            "rule": "pick",
            "min": 0,
            "max": 1,
            "from": "A"
          }
        ],
        "input_descriptors": [
          {
            "id": "SphereonWalletId",
            "purpose": "Checking your Sphereon Wallet information",
            "name": "Wallet Identity",
            "group": [
              "A"
            ],
            "schema": [
              {
                "uri": "https://sphereon-opensource.github.io/ssi-mobile-wallet/context/sphereon-wallet-identity-v1.jsonld"
              }
            ]
          }
        ]
      }
    }
  },
...

However, the Sphereon Wallet App now hangs and times out with a 504 gateway error when trying to fetch this. Fetching it at the same URL from my laptop works OK. Strange. Does the wallet use a proxy?

from oid4vc-demo.

The demo agent doesn't have any definition with ID sphereonWallet though. Is that definition missing from the open source?

from oid4vc-demo.