Add Oscore SecurityInfo support to Server and BS Server demo #1211
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support to OSCORE for Server and Bootstrap Server demo. (#1203).
With this PR a client should be able to connect to both server using OSCORE.
But this PR does not contain support to write OSCORE object during bootstrap session. (This will be done in another PR)
This is work in progress, for now we are only able to provide Sender ID, Recipient ID, Master Secret.it is only possible to connect to server demo (not bootstrap server). (because SecurityInfo only add context toOscoreServerHandler.getContextDB()
not toOscoreBootstrapHandler
.context is not persisted on restart so you need to delete/recreate your security info to make it work again.So no need to invest more time for now, let's focus on OscoreStore.