Matthew Miller

Looks good to me, thank you Emil for the thorough collection of examples!

Hello @Satistile, what's the base64url value of `pub_key` coming out of `db_calls.get_key(logged_in_user_id)`? Sharing that might help troubleshoot what's going on here.

Without a sample value for `pub_key` I can't assist in troubleshooting any further. Please feel free to reopen this issue if you are able to provide such a value.

This is bizarre, that `pub_key` is the following hex: ``` 3059301306072a8648ce3d020106082a8648ce3d03010703420004f003d8ccd5bf3a42337fc722cee362c2a309864f08a88c4289576397152e9581f47e94ddaf45b8e9f23cf57a28b2537caf557856ed43ad471d735bc71a71c1d2 ``` When I drop that hex into https://cbor.me the site says the bytes are "the value -17", with "90...

Hello @Satistile, is this still an issue for you? ```py # registration db_calls.add_key(logged_in_user_id, credential["response"]["publicKey"]) ``` ```py # authentication pub_key = base64url_to_bytes(db_calls.get_key(logged_in_user_id)) ``` The only thing I can suggest is that...

Hello @Densaugeo and @Satistile, I'm finally understanding what's going on now. The output of `.getPublicKey()` is DER-encoded bytes comprising a `SubjectPublicKeyInfo` data structure. Inside this structure is the same public...

Say, what encoding is used on the `challenge` query parameter to get bytes to "`:Y2hhbGxlbmdl:`" format?

Would a lack of open documentation for developer reference preclude inclusion of e.g. mdoc-related identifiers from the registry? I'm not saying I agree or disagree with that, just thinking through...

I also think we should keep the requirement that an entry in the registry be freely available. Making DC API a "pay to play" API if a more popular protocol...

> We can avoid that if we just specify our objects are JSON serializable from the start Will it be feasible to define this behavior in the DC API spec...