Christian Bormann
Christian Bormann
> > Another way could be to define this as a processing rule within the SD-JWT VC. > > > I think this is also what was done for ISO...
> So, I still don't agree with the assessment here that it's not needed. All the formats require some validation to happen at some point, and that needs to be...
> That's not how it works at least on Apple's platforms. The initial validation is done by OS level framework. Eventually, once deemed safe, the data is passed to the...
To clarify since that came up in the discussion last Thursday and I was asked to add it as a comment here in the discussion: One of the biggest fears...
We had a bit more discussion on this after the call and I think the cleanest solution would be to include the encryption key in the proof types (jwt proof...
I just came across a similar issue -> +1 for the Feature, especially with the ability/freedom to use other backends.
If I recall correctly, someone mentioned a week ago that this is already defined/proposed somewhere for mDoc? Might've been @martijnharing (sorry if I recalled and tagged you incorrectly)?
> Requesting multiple credentials in a single request seems confusing and complex (to both the site developer and the user) and hostile to the user. Making requests about a single...
There was some discussion on this in the prior issue/PR: #404
> Based on my implementation experience, having nonce endpoint issue nonces/challenges that can be used by any session is a big red flag. It is not a big issue on...