-
-
like biometrics-based binding
Torsten started with this example in [this PR in sd-jwt repo](https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/210/files) but i do not think it's viable…
-
- **I'm submitting a ...**
- [x] bug report
- [ ] feature request
- [ ] question about the decisions made in the repository
- [ ] question about how to use this project
- **Summary**
…
-
As an Issuer, Keycloak exposes some metadata to describe the credentials that it can issue. The "display" array property is particularly useful in that it allows interacting wallets to style credentia…
-
One of the quirks of SD-JWT is that the disclosures themselves can be encoded however the issuer deems right. There is no necessity to define rules like always using minified JSON or certain character…
c2bo updated
7 months ago
-
Hi,
we come across some issues with the way the constraints element. In my opinion, it mixes expressions for filtering Credentials with a definition of the claims a verifier wants to get selectivel…
-
raised by @Sakurann among others: should we define a registry of types of credentials, which may have different sorts of privacy implications and necessary protections?
It seems like a government-i…
-
Draft 13 specifies that authorization_details, among other claims, it must contain either
> a **credential_configuration_id** referencing a specific credential configuration in issuer's credential_…
-
Hi Nikos!
As commented before I attach some things that I have found that may need some clarification or modification:
1. How is authentication done in Authorization Code Flow? Is it done via id…
-
In the context of eIDAS 2, we require a Wallet/Issuer Trust Evidence, basically a key attestation made by the Wallet Provider ensuring that keys used for keybinding really reside in a trustworthy key …