Logging for prover role

README.md

@@ -12,6 +12,8 @@ Make sure to read the [best practices](/docs/BestPractices.md) to be used when p
 
 If you are upgrading from a previous release, take a look at the [migration guide](/docs/MigrationGuide.md).
 
+For information about prover-role functionality (when VC-AuthN responds to proof requests), see the [prover role logging documentation](/docs/ProverRoleLogging.md).
+
 ## Pre-requisites
 
 - A bash-compatible shell such as [Git Bash](https://git-scm.com/downloads)
@@ -105,6 +107,23 @@ curl -X 'POST' \
 
 After all these steps have been completed, you should be able to authenticate with the demo application using the "Verified Credential Access" option.
 
+## Advanced Features
+
+### Prover Role (Trusted Verifier Credentials)
+
+VC-AuthN can also act as a **prover**, holding credentials in its own wallet and responding to proof requests from external verifiers. This is useful for trusted verifier networks where VC-AuthN must prove its authorization status.
+
+For detailed information about prover-role functionality, testing, and configuration, see the [Prover Role Logging documentation](docs/ProverRoleLogging.md).
+
+**Quick Test**: To test prover-role functionality with the bootstrap script:
+```bash
+cd docker
+TEST_PROVER_ROLE=true \
+LEDGER_URL=http://test.bcovrin.vonx.io \
+TAILS_SERVER_URL=https://tails-test.vonx.io \
+./manage bootstrap
+```
+
 ## Debugging
 
 To connect a debugger to the `vc-authn` controller service, start the project using `DEBUGGER=true ./manage single-pod` and then launch the debugger.

docker/docker-compose.yaml

@@ -175,6 +175,7 @@ services:
       - ACAPY_AUTO_VERIFY_PRESENTATION=true
       - ACAPY_AUTO_RESPOND_CREDENTIAL_OFFER=true
       - ACAPY_AUTO_STORE_CREDENTIAL=true
+      - ACAPY_AUTO_RESPOND_PRESENTATION_REQUEST=true
       - ACAPY_WALLET_STORAGE_TYPE=${WALLET_TYPE}
       - ACAPY_READ_ONLY_LEDGER=true
       - ACAPY_GENESIS_TRANSACTIONS_LIST=/tmp/ledgers.yaml

docker/manage

@@ -197,13 +197,13 @@ configureEnvironment() {
 # This must be called AFTER setNgrokEndpoints to ensure URLs are properly set
 finalizeEnvironment() {
   # Controller Webhook URL: Append API Key if present
-  if [ ! -z "${CONTROLLER_API_KEY}" ] && [[ "${CONTROLLER_WEB_HOOK_URL}" != *"#"* ]]; then
+  if [ -v CONTROLLER_API_KEY ] && [ -n "${CONTROLLER_API_KEY}" ] && [[ "${CONTROLLER_WEB_HOOK_URL}" != *"#"* ]]; then
     export CONTROLLER_WEB_HOOK_URL="${CONTROLLER_WEB_HOOK_URL}#${CONTROLLER_API_KEY}"
   fi
 
   # Agent Admin Mode: Append API Key if present
   export AGENT_ADMIN_MODE="admin-insecure-mode"
-  if [ ! -z "${AGENT_ADMIN_API_KEY}" ]; then
+  if [ -v AGENT_ADMIN_API_KEY ] && [ -n "${AGENT_ADMIN_API_KEY}" ]; then
     export AGENT_ADMIN_MODE="admin-api-key ${AGENT_ADMIN_API_KEY}"
   fi