-
Notifications
You must be signed in to change notification settings - Fork 52
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.
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
Bootstrap Server Account purge #39
Comments
I also wonder how you change credentials? For example X.509 certificates have an expiration date. |
Yes I agree, there are discussions in OMA DM at that time on that point :-) !! |
Closed
Addressed in the current TS. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Technical Specification in chapters 5.2.2.3 Client Initiated Bootstrap and 5.2.2.4 Server Initiated Bootstrap states:
But the Bootstrap Server Account is stored in the LWM2M Security which is not accessible to any LWM2M Server.
Moreover the same chapters write:
Thus the whole unbootstrapping procedure described in chapter E.1.3 seems unreachable since there will never be a bootstrap server to remove a LWM2M server the client is registered to.
It is also impossible to add new LWM2M servers to LWM2M clients during their lifetime without factory-resetting them.
The text was updated successfully, but these errors were encountered: