[java-idp-plugin-vci] branch main updated: Instructions updated, each credential does not carry 'status' claim anymore

[Codeberg]

This is an automated email from the git hooks/post-receive script.

codeberg pushed a commit to branch main
in repository java-idp-plugin-vci.

View the commit online:
https://codeberg.org/Shibboleth/java-idp-plugin-vci/commit/6cba7b7115b8a3614dfd197816e4d5a9414054f0

The following commit(s) were added to refs/heads/main by this push:
     new 6cba7b7  Instructions updated, each credential does not carry 'status' claim anymore
6cba7b7 is described below

commit 6cba7b7115b8a3614dfd197816e4d5a9414054f0
Author: Janne Lauros <janne.lauros at csc.fi>
AuthorDate: Wed Sep 9 10:54:20 2026 +0300

    Instructions updated, each credential does not carry 'status' claim anymore
---
 README.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index dc490ad..2ca5797 100644
--- a/README.md
+++ b/README.md
@@ -774,8 +774,8 @@ And you release it to the wallet in *conf/attribute-filter.xml*. This flow reads
 **File(s):** *conf/relying-party.xml*, *conf/openid-vci.properties*
 **Format:** Native Spring, Spring Properties
 
-Every credential this plugin issues carries a `status` claim that names one slot of a Status
-List, as in [draft-ietf-oauth-status-list](https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/).
+Credentials this plugin issues carry a `status` claim that names one slot of a Status List, as
+in [draft-ietf-oauth-status-list](https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/).
 The credential endpoint allocates a slot for every credential it signs, unless the credential
 is told not to take one. The Status List is part of a working installation rather than an extra
 you opt into. Turning it off for one credential, or making it something each credential opts
@@ -839,8 +839,8 @@ and same consequences as in [Signing keys](#signing-keys) above.
 #### Finding the slot of a credential
 
 A Status List has bits and nothing else in it, so the mapping from a credential to its slot is
-in the assignment records. The credential endpoint writes one record per issuance and nothing
-in the IdP reads them back.
+in the assignment records. The credential endpoint writes one record per issuance that took
+slots, and nothing in the IdP reads them back.
 
 Shibboleth is not a register of issued credentials and it is not meant to become one. Somebody
 decides one day that a credential has to be withdrawn and the reason may be anything you are
@@ -1353,7 +1353,8 @@ Issues the credential. A `POST` of `application/json` to
 
 The wallet forms the request and its parameters are the ones of the specification. Two things
 of it are worth knowing. Only key proofs of type `jwt` are supported and one credential is
-issued per proof, each of them taking a status list slot of its own. Member
+issued per proof, each of them taking a status list slot of its own when the credential takes
+slots at all. Member
 `credential_response_encryption` is parsed and written to the log and nothing else is done with
 it, an encrypted credential response is not implemented.
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.