From c5ee0552b4497a79164745a84b3805fdc8163037 Mon Sep 17 00:00:00 2001 From: "David J. Allen" Date: Tue, 3 Dec 2024 13:37:58 -0700 Subject: [PATCH] readme: updated example to use coredhcp --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 840558e..d040037 100644 --- a/README.md +++ b/README.md @@ -57,9 +57,9 @@ Once the server is up and listening for HTTP requests, you can try making a requ ```bash export ACCESS_TOKEN=eyJhbGciOiJIUzI1NiIs... -curl http://127.0.0.1:3334/generate?target=dnsmasq -X GET -H "Authorization: Bearer $ACCESS_TOKEN" --cacert ochami.pem +curl http://127.0.0.1:3334/generate?target=coredhcp -X GET -H "Authorization: Bearer $ACCESS_TOKEN" --cacert ochami.pem # ...or... -./configurator fetch --target dnsmasq --host http://127.0.0.1:3334 --cacert ochami.pem +./configurator fetch --target coredhcp --host http://127.0.0.1:3334 --cacert ochami.pem ``` This will do the same thing as the `generate` subcommand, but through a GET request where the file contents is returned in the response. The access token is only required if the `CONFIGURATOR_JWKS_URL` environment variable is set when starting the server with `serve`. The `ACCESS_TOKEN` environment variable is passed to `curl` using the `Authorization` header and expects a token as a JWT.