From 1a3c7c452f1ba851854dc10b5776bc609a9150f4 Mon Sep 17 00:00:00 2001 From: Wout Slakhorst Date: Wed, 18 Dec 2024 14:06:25 +0100 Subject: [PATCH] update registrationParam to pex mapping --- docs/pages/deployment/discovery.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/pages/deployment/discovery.rst b/docs/pages/deployment/discovery.rst index fc7b4d049..973607425 100644 --- a/docs/pages/deployment/discovery.rst +++ b/docs/pages/deployment/discovery.rst @@ -60,7 +60,8 @@ Optionally, a POST body can be provided with registration parameters, e.g.: This can be used to provide additional information. All registration parameters are returned by the search API. The ``authServerURL`` is added automatically by the Nuts node. It's constructed as ``https:///oauth2/``. -Registration parameters can only be used if the specific parameters and/or ``DiscoveryRegistrationCredential`` are required by the Presentation Definition. +Registration parameters can only be used if a specific parameters and/or ``DiscoveryRegistrationCredential`` are required by the Presentation Definition. +The key provided in the POST call can be matched by the path of a field in the Presentation Definition. So ``endpoint`` in the example above can be matched by the path ``$.credentialSubject.endpoint``. Once registered, future refreshes will be done automatically by the Nuts node. These refreshes could fail because of various reasons. You can check the status of the refreshes by querying the service, e.g.: