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.

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

FW-767. Implementation of RS role of OSCORE profile of ACE framework. #434

Open
wants to merge 16 commits into
base: develop
Choose a base branch
from

Conversation

malishav
Copy link
Contributor

@malishav malishav commented Jul 31, 2018

This PR adds support for a 3-party authorization by implementing OSCORE profile of ACE framework.

The role of RS is co-located with a 6TiSCH node, implemented as part of this PR.
The role of AS is co-located with JRC, implemented as part of openwsn-sw repository.
The role of Client is implemented as part of coap repository.

malishav added 16 commits July 27, 2018 10:39
The implementation of the RS role of the ACE framework.
RS exposes "/resource1" that should only be accessed over an OSCORE
channel. The security context to establish this channel is communicated
to the RS by the Client by a POST to /token resource, with payload
containing the access token. The access token, encrypted and
authenticated with a key shared between the RS and the AS, contains
OSCORE parameters.
When a protected resource is accessed over unprotected transport (i.e.
without OSCORE), RS returns 4.01 Unauthorized error with payload
containing the AS Info CBOR object. This object encodes the URI of the
AS, where access token can be requested.
The file will contain both encoding and decoding functions.
Add special type, not defined in OSCORE, to derive ACE keys. This is a
custom way of defining keys shared between the AS and RS, as part of the
ACE authorization framework.
CWT is a COSE Encrypt0 object. The implementation of the decoding
routing is quite conservative in what it accepts.
Tail of the linked list was skipped.
@changtengfei
Copy link
Member

Can one of the admins verify this patch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants