-
The `ttl` property seems to be ineffective, could lead to confusion (false expectations), and might be a layering violation. I suggest we remove it and note that other mechanisms could be used to achi…
-
# Consider supporting federated login without IDP APIs
This is meant to be a conversation-starter around how we can preserve federated login scenarios without adding IDP APIs.
I don't think this n…
-
## Abstract
The [Verifiable Credentials v2.0 test suite](https://github.com/digitalbazaar/vc-data-model-2-test-suite) provides a mechanism to test if an issuer or verifier is conformant with the Ve…
-
## Proposed comment
Internationalization Considerations
https://w3c.github.io/vc-bitstring-status-list/#internationalization-considerations
> Readers are urged to familiarize themselves with th…
-
Hi folks,
It looks like between:
```
ECDSA Cryptosuite v2019
Achieving Data Integrity using ECDSA with NIST-compliant curves
Final Community Group Report 24 July 2022
https://www.w3.org/comm…
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1720
### Original Reporter: KristinaYasuda
should be jwk thumbprint uri
-
When you do Verification of a revoked Verifiable Credential - if the credential is properly revoked then you'll get a 400 "message": "Invalid Input!"
However this is the same message I seem to get …
-
In my understanding a credential validity determines time range in which claims attributed to a subject are truthful. If validity is not specified then the statements are truthful with no regard on t…
-
Currently the Accept header is used in Issue and Verify requests to specify the format of the verifiable credential. Legitimate values are vc (for json VCs with linked data proofs), vc-jwt, and (pendi…
-
If `url` is configured with port `443`, private keys can't be resolved for created did:web DIDs. If 443 is removed from the URL, private keys can be resolved again.
Config:
```yaml
url: https://n…