Very interesting! > The Concise Binary Object Representation (CBOR) key structures [RFC8949] and > Header Parameters for Carrying and Referencing X.509 Certificates [RFC9360] that > have been defined in *COSE currently do not support all the properties made available in [OIDC-FED].* ... > COSE_TRUSTCHAIN = [ N * jws :bstr ] > The variable N represent the number of Entity Statements that a Trust Chain can contain. The contents of "bstr" are the bytes representing a JWS.
Are these always JWTs, can they be JWS over non JSON content types? Why not allow CWT or CoseSign 1 here? Super cool to see mDoc and OIDC alignment! OS On Tue, Jul 11, 2023 at 7:31 AM Giuseppe De Marco <[email protected]> wrote: > Hi all, > > I have been working on a small draft needed for enabling OpenID Conenct > Federation 1.0 Trust Chains in COSE Sign documents. > > Below the link to the draft: > > https://peppelinux.github.io/draft-demarco-cose-header-federation-trust-chain/draft-demarco-cose-header-federation-trust-chain.html > > Where the link to the the repository of the project is the one below: > > https://github.com/peppelinux/draft-demarco-cose-header-federation-trust-chain > > The first implementation will be achieved in the following open source > python package: > https://github.com/IdentityPython/pyMDOC-CBOR > > I would like the COSE working group to adopt this document. > > Thanking you for your precious attention, I am available for a > presentation/discussion of the proposed document to provide further details > or information, if these are not already intelligible from the this initial > draft or any further information about OIDC Federation if of interest. > > Regards > _______________________________________________ > COSE mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/cose > -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
