-
**Configuration:**
branch sd_issue#2681
EUDI profile and PID from test 8 in Wallet Tests for OIDC4VCI compliance
qr code for EUDI profile
![image](https://github.com/TalaoDAO/AltMe/assets/49282360…
-
Section 6 only defines 3 response_types that return VP tokens:
whereas 'A.4. Combining this specification with SIOPv2' says that `response_type=id_token` can also return a VP token:
It s…
jogu updated
7 months ago
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1744
### Original Reporter: KristinaYasuda
in VCI, we have user\_pin\_required feature. given pin is a useful feat…
-
value of the parameter `defaultDid`
```
......
"credentialManifestSupport": false,
"userPinDigits": "4",
"defaultDid": "urn:ietf:params:oauth:client-…
-
**_301 Moved Permanently_: The [updated version of the Threat Model](https://github.com/w3c-cg/threat-modeling/blob/main/models/decentralized-identities.md) is in the [Threat Model Community Group](ht…
-
Currently, implementations can protect the PoP for wallet attestations (https://datatracker.ietf.org/doc/draft-looker-oauth-attestation-based-client-auth) by:
- making it short lived
- making it o…
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1967
### Original Reporter: peppelinux
In [Section 8.2](https://openid.bitbucket.io/connect/openid-4-verifiable-pr…
-
Today each message has its own signature. This is convenient as each message is independently verifiable, but also carries some overhead that we may be able to reduce.
OAuth 2.0 and OIDC are widely…
-
flows defined in this repository use artifacts defined in other specifications in the context different from what is intended in original specifications, and that is confusing and feels like a patchwo…
-
### Description
In the SIOPv2 cross-device scenario, the Relying Party converts its SIOP Request into a QR Code which presented on one device so that it can be scanned using a second device. The Prov…