Skip to content

Gaia-X registry path is hardcoded #72

@markendos

Description

@markendos

Hi, when trying to verify VCs against a Gaia-X registry, I was not able to use a specific environment (e.g. v1, v1-staging, development) from the available Gaia-X instances since apparently v2 environment endpoint is hardcoded:

const GAIAX_REGISTRY_TRUSTANCHOR_FILE = "/v2/api/trustAnchor/chain/file"

It would be nice to allow full path customization from the service configuration or some approach to make this more flexible in future releases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions