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.

Sign up for GitHub

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

update registrationParam to pex mapping #3624

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

update registrationParam to pex mapping #3624

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/pages/deployment/discovery.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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://<config.url>/oauth2/<subject_id>``.
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``.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find the first sentence hard to read.

Suggested change
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``.
The registration parameters should match the ``credentialSubject`` definition for the ``DiscoveryRegistrationCredential`` 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.:
Expand Down
Loading