oneM2M TS-0009Release Notes diff from v5.1.0 to v5.1.0oneM2M TS-0009Release Notes diff from v5.1.0 to v5.1.0When sending the credential to be checked by the Registrar CSE, Proxy-Authorization header should be used as specified in HTTP/1.1 (see IETF RFC 7235 [4]).
When sending the credential to be checked by Hosting CSE, Authorization header should be used as specified in HTTP/1.1 [4].
When the credential to be checked by Hosting CSE is an Access Token which is compatible with Oauth 2.0 framework (see IETF RFC 6750 [5]), the Bearer authentication scheme shall be used as specified in Oauth 2.0 framework.
NOTE: The oneM2M Security Solutions [2] does not provide any details on usage or provisioning of the token.
oneM2M primitive parameters contained in HTTP messages may be protected by TLS in a hop-by-hop manner. For the details, see the oneM2M Security Solutions specification [2].
NOTE: Some provisioning schemes of oneM2M TS-0003 [2] enable the provisioning of end-to-end credentials, but protocols to establish security associations between non-adjacent nodes are not addressed by oneM2M in the present document.