@techreport{chu-oauth-subject-key-binding-00, number = {draft-chu-oauth-subject-key-binding-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-chu-oauth-subject-key-binding/00/}, author = {Cheng-Kang Chu and Li Ruochen and Haiguang Wang and Tieyan Li}, title = {{OAuth Subject Signing Key Binding for Resource Servers}}, pagetotal = 30, year = 2026, month = sep, day = 1, abstract = {Resource servers in OAuth deployments sometimes receive application- layer authorization evidence that is digitally signed by the subject represented by an access token. Verification of such evidence requires the resource server to obtain a trusted public signing key that is bound to that subject. This specification defines the subject\_keys parameter, by which an OAuth authorization server conveys one or more subject public signing keys to a resource server. The parameter can be carried as a claim in a JWT access token or as a member of a token introspection response. The resulting key binding is scoped to the authorization server, token subject, resource server audience, and token validity context. This specification does not define a public-key enrollment protocol or the syntax and semantics of the application-layer authorization evidence. It also does not use the OAuth cnf claim, which identifies a proof-of-possession key held by the presenter of a token.}, }