Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Incorrect CoAP result on security object action made by the DM server #440

Closed
fdur opened this issue May 9, 2019 · 2 comments
Closed

Incorrect CoAP result on security object action made by the DM server #440

fdur opened this issue May 9, 2019 · 2 comments
Labels
bug

Comments

@fdur
Copy link
Contributor

fdur commented May 9, 2019 •
edited
Loading

According to LwM2M 1.0.2 specification:

The LwM2M Client MUST reject with an “Unauthorized” response code any LwM2M Server operation on the Security Object (ID: 0).

In current source code, "Not Found" is returned
@fdur fdur changed the title Inccorect CoAP result on security object action made by the DM server Incorrect CoAP result on security object action made by the DM server May 9, 2019
fdur added a commit to fdur/wakaama that referenced this issue May 9, 2019
@fdur
Fix for issue eclipse-wakaama#440: Crash with client in DTLS when "qu…
37d1002 
…it" is usedIncorrect CoAP result on security object action made by the DM server

Signed-off-by: Frederic DUR <fdur@sierrawireless.com>
@sbernard31 sbernard31 added the bug label Nov 3, 2020
@sbernard31
Copy link
Contributor

Not a big bug but probably better to fix it.
This is also true for LWM2M 1.1.

qleisan pushed a commit to qleisan/wakaama that referenced this issue Feb 4, 2021
@fdur
Fix for issue eclipse-wakaama#440: Crash with client in DTLS when "qu…
6c50317 
…it" is usedIncorrect CoAP result on security object action made by the DM server

Signed-off-by: Frederic DUR <fdur@sierrawireless.com>
@qleisan qleisan mentioned this issue Feb 4, 2021
Merged
@qleisan
Copy link

qleisan commented Feb 4, 2021

@fdur thanks for reporting this bug! @sbernard31 please close once #533 is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sbernard31 @fdur @qleisan