# US 2026/0100833 A1 · Privacy preserving credential token issuance > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2026/0100833 A1 - Document ID: US20260100833A1 - Status: Published application - Kind: A1 - Application number: 18/906,336 - Filed: 2024-10-04 - Published: 2026-04-09 - Earliest claimed: 2024-10-04 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: Alessandro Sorniotti; Elli Androulaki; Kaoutar El Khiyaoui; Yacov Manevich; Jens Jelitto; Ilie Circiumaru; Pasquale Convertini - Web page: https://patentgrep.com/patent/US20260100833A1 ## CPC - H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy - H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying} - H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Mechanisms are provided for re-issuance of credentials in a data network. The mechanisms receive, from a requester entity, a first request to re-issue a target credential in a plurality of credentials of a public credential listing. Any entity, in a plurality of entities, can request re-issuance of any credential in the plurality of credentials and have the credential successfully re-issued to that entity. The mechanisms, in response to the request to re-issue the target credential, re-randomize an original public key associated with the target credential to generate a re-randomized public key. The mechanisms generate a new credential based on the target credential but with the original public key replaced with the re-randomized public key. The mechanisms provide the new credential to the requester entity. The requester entity can use the new credential for authentication successfully only if the requester entity is an owner of the target credential. ## Claims ### Claim 1 A method, in a data processing system, for re-issuance of credentials in a data network, the method comprising: receiving, from a requester entity, a first request to re-issue a target credential in a plurality of credentials of a public credential listing, wherein any entity, in a plurality of entities, can request re-issuance of any credential in the plurality of credentials and have the credential successfully re-issued to that entity; in response to the request to re-issue the target credential, re-randomizing an original public key associated with the target credential to generate a re-randomized public key; generating a new credential based on the target credential but with the original public key replaced with the re-randomized public key; and providing the new credential to the requester entity, wherein the requester entity can use the new credential for authentication transactions successfully only if the requester entity is an owner of the target credential. ### Claim 2 (depends on 1) The method of claim 1, wherein the first request is one of a plurality of requests from the same requester entity, each request in the plurality of requests requesting re-issue of a corresponding other target credential. ### Claim 3 (depends on 2) The method of claim 2, wherein the plurality of requests comprises the first request and one or more second requests that are decoy requests submitted to hide the first request within the plurality of requests. ### Claim 4 (depends on 1) The method of claim 1, wherein generating the new credential comprises performing a blind signing of the new credential by the data processing system, wherein the blind signing comprises the data processing system signing the new credential without knowing whether the requester entity is an identity owner of the target credential. ### Claim 5 (depends on 4) The method of claim 4, wherein after blind signing of the new credential, the new credential is a reissued credential that is not able to be related to the target credential via a public key since the original public key and the re-randomized public key are uncorrelatable. ### Claim 6 (depends on 1) The method of claim 1, wherein the data processing system publishes all certified public keys and credentials, for all holders that have been issued a credential, in a published listing data structure accessible to all users. ### Claim 7 (depends on 1) The method of claim 1, wherein the requesting entity is not the identity holder of the target credential, and wherein when the requesting entity presents the new credential to a verifier, the requesting entity provides an invalid presentation of the new credential. ### Claim 8 (depends on 1) The method of claim 1, wherein: the request is one of a plurality of requests from the requesting entity, which are submitted to the data processing system, each request in the plurality of requests is directed to a different target credential, each request is successful and generates a corresponding re-issued credential that is provided to the requesting entity, the requesting entity is an identity holder associated with the target credential, and the requesting entity uses the new credential in a presentation of the new credential as part of an interaction with a verifier and discards the other re-issued credentials. ### Claim 9 (depends on 1) The method of claim 1, wherein successful collusion between an issuer of credentials and a verifier to generate a profile of an identity holder is prevented by the method since the new credential is not able to be correlated, by the issuer or verifier, with the target credential. ### Claim 10 (depends on 1) The method of claim 1, wherein the target credential is a first JavaScript Object Notation (JSON) Web Token (JWT) and wherein the new credential is a second JWT comprising a same header, same attributes, but different public key and signature than the first JWT. ### Claim 11 A computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed in a data processing system, causes the data processing system to: receive, from a requester entity, a first request to re-issue a target credential in a plurality of credentials of a public credential listing, wherein any entity, in a plurality of entities, can request re-issuance of any credential in the plurality of credentials and have the credential successfully re-issued to that entity; re-randomize, in response to the request to re-issue the target credential, an original public key associated with the target credential to generate a re-randomized public key; generate a new credential based on the target credential but with the original public key replaced with the re-randomized public key; and provide the new credential to the requester entity, wherein the requester entity can use the new credential for authentication transactions successfully only if the requester entity is an owner of the target credential. ### Claim 12 (depends on 11) The computer program product of claim 11, wherein the first request is one of a plurality of requests from the same requester entity, each request in the plurality of requests requesting re-issue of a corresponding other target credential. ### Claim 13 (depends on 12) The computer program product of claim 12, wherein the plurality of requests comprises the first request and one or more second requests that are decoy requests submitted to hide the first request within the plurality of requests. ### Claim 14 (depends on 11) The computer program product of claim 11, wherein generating the new credential comprises performing a blind signing of the new credential by the data processing system, wherein the blind signing comprises the data processing system signing the new credential without knowing whether the requester entity is an identity owner of the target credential. ### Claim 15 (depends on 14) The computer program product of claim 14, wherein after blind signing of the new credential, the new credential is a reissued credential that is not able to be related to the target credential via a public key since the original public key and the re-randomized public key are uncorrelatable. ### Claim 16 (depends on 11) The computer program product of claim 11, wherein the data processing system publishes all certified public keys and credentials, for all holders that have been issued a credential, in a published listing data structure accessible to all users. ### Claim 17 (depends on 11) The computer program product of claim 11, wherein the requesting entity is not the identity holder of the target credential, and wherein when the requesting entity presents the new credential to a verifier, the requesting entity provides an invalid presentation of the new credential. ### Claim 18 (depends on 11) The computer program product of claim 11, wherein: the request is one of a plurality of requests from the requesting entity, which are submitted to the data processing system, each request in the plurality of requests is directed to a different target credential, each request is successful and generates a corresponding re-issued credential that is provided to the requesting entity, the requesting entity is an identity holder associated with the target credential, and the requesting entity uses the new credential in a presentation of the new credential as part of an interaction with a verifier and discards the other re-issued credentials. ### Claim 19 (depends on 11) The computer program product of claim 11, wherein successful collusion between an issuer of credentials and a verifier to generate a profile of an identity holder is prevented by the method since the new credential is not able to be correlated, by the issuer or verifier, with the target credential via a public key. ### Claim 20 An apparatus comprising: at least one processor; and at least one memory coupled to the at least one processor, wherein the at least one memory comprises instructions which, when executed by the at least one processor, cause the at least one processor to: receive, from a requester entity, a first request to re-issue a target credential in a plurality of credentials of a public credential listing, wherein any entity, in a plurality of entities, can request re-issuance of any credential in the plurality of credentials and have the credential successfully re-issued to that entity; re-randomize, in response to the request to re-issue the target credential, an original public key associated with the target credential to generate a re-randomized public key; generate a new credential based on the target credential but with the original public key replaced with the re-randomized public key; and provide the new credential to the requester entity, wherein the requester entity can use the new credential for authentication transactions successfully only if the requester entity is an owner of the target credential.