For major re-configurations or variations from the default behavior of DIDKit, modifying the code and compiling your own binaries is required.
For a short but growing list of minor options, however, runtime configuration of DIDKit behavior and security policies is possible. Feel free to open issues on DIDKit's GitHub repo if you are experimenting with DIDKit and have pain points that would be served by additional runtime configuration options.
For all outbound HTTP requests, DIDKit relies on the upstream
reqwestchecks the environmental variables in DIDKit's environment for the variables
HTTPS_PROXYto route http and https traffic respectively. If you have set up such a proxy, including a reverse proxy or SOCKS service, you can set the appropriate environmental variable(s) and assume
reqwestwill route appropriately.
This proxying is unavailable in the npm package
For more information about how
reqwesthandles proxies, see the proxies section of the
reqwestdocs on docs.rs, the Rust ecosystem documentation repository.