obgm
commented
3 months ago To clarify: The token in a CoAP message is used to match a CoAP response to the CoAP request that has triggered this reponse. By this, it is inherently tied to the CoAP messaging layer. According to your description it seems that you want to try to pass an authorization token (sometimes inaccurately called access token) for some application protocol. This is transparent to CoAP and therefore, libcoap has no direct support for this (although you can retrieve the token in the CoAP PDU in the request handler to achieve what you are trying to do). Your scenario warrants for using a POST request to convey your token.
As a side note: There is a series of IETF specifications that detail how to use CoAP (or other REST-friendly transport protocols) to not only transfer authorization tokens but also create a security association between communication peers based on this token. This is described in RFC 9200 ff. There is also an implementation of the DTLS profile based on libcoap.
Is your feature request related to a problem? Please describe.
Right now I am trying to set the access token in client side so that I can use the same access token in server side and perform a curl request. When I investigated I found there is this api coap_pdu_get_token() results a token that will not be useful for me because in coap_pdu_t there are 2 member variables actual_token which is associated with coap_pdu_get_token but I want to access the uint_8 token member variable inside the coap pdu. I didn't find any option nor a api to do that.
Describe the solution you would like
If we add a option called COAP_OPTION_ACCESS_TOKEN which can be set in client side and used in server side would be a good fit.
Describe alternatives you have considered
I am trying to use the COAP_OPTION_URI_QUERY for this it should work but developers may get confused.
If there are any other existing alternative for this let me know.