It is often the case that intermediaries need details about token issuers so that they can accept their tokens. The simplest case is a CDN that wants to allow a user to configure tokens to accept.
The SVA is working on a configuration API for CDNs that seeks to standardize some aspects of configuration and they need to know what the metadata for CATs looks like.
It might be useful to have an encapsulation format that contains the relevant keys and issuer names all grouped together. In CDNI, this largely accomplished with a map of JWKs. The CAT has a larger variety of keys, though. I'm making a note here to think about it, though.
It is often the case that intermediaries need details about token issuers so that they can accept their tokens. The simplest case is a CDN that wants to allow a user to configure tokens to accept.
The SVA is working on a configuration API for CDNs that seeks to standardize some aspects of configuration and they need to know what the metadata for CATs looks like.
It might be useful to have an encapsulation format that contains the relevant keys and issuer names all grouped together. In CDNI, this largely accomplished with a map of JWKs. The CAT has a larger variety of keys, though. I'm making a note here to think about it, though.