Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AS: accessing configuration from verifiers #384

Open
thomas-fossati opened this issue May 10, 2024 · 3 comments
Open

AS: accessing configuration from verifiers #384

thomas-fossati opened this issue May 10, 2024 · 3 comments

Comments

@thomas-fossati
Copy link
Contributor

I would like to use the AS configuration file to describe the parameters for my verifier.

Something like:

{
  "//": "global AS config"

  "work_dir": "...",

  "//": "per-verifier stanzas"
  "verifiers": {
    "cca": {
      "veraison": {
        "endpoint": "https://veraison.example/challenge-response/v1/newSession",
        "api-token": "/path/to/api/token.jwt"
        "tls-config": {
          "ca-certs": "/path/to/ca.pem",
          "//": "etc."
        }
      }
    }
  }
}

At present, this is not supported. Is that a conscious design decision, or is it because no one had this need before?

A (less intrusive) alternative would be to have a separate configuration file and pass it to my verifier in an environment variable.

Would such an approach be preferable?

@Xynnn007
Copy link
Member

@thomas-fossati Currently, the address for verasion is set by env key VERAISON_ADDR and we haven't supported the config. The reason might be no one had this need.

For a long term design, I prefer to have a pure rust CCA verifier handler/implementation to replace veraison for CCA.

Kevin (Hi @kevinzs2048 , hopefully I pinged the right person) could probably give more contexts.

@thomas-fossati
Copy link
Contributor Author

@thomas-fossati Currently, the address for verasion is set by env key VERAISON_ADDR and we haven't supported the config. The reason might be no one had this need.

OK, thanks for confirming this is accidental and there is no design "barrier" to such an approach.

For a long term design, I prefer to have a pure rust CCA verifier handler/implementation to replace veraison for CCA.

Yes, this is in progress. I have just started integrating Veraison's rust-ccatoken into Trustee.

But we still want to allow both options (i.e., remote and embedded CCA verifiers), hence the question.

Kevin (Hi @kevinzs2048 , hopefully I pinged the right person) could probably give more contexts.

Yes, you did. Kevin and I are in the same team at Linaro :-)

@fitzthum
Copy link
Member

Yeah I think I would prefer configuration through the config file over an environment variable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants