Skip to content

Comments

COAP-40. Implement Client role of OSCORE profile of ACE framework.#26

Open
malishav wants to merge 9 commits intoopenwsn-berkeley:developfrom
malishav:develop_COAP-40
Open

COAP-40. Implement Client role of OSCORE profile of ACE framework.#26
malishav wants to merge 9 commits intoopenwsn-berkeley:developfrom
malishav:develop_COAP-40

Conversation

@malishav
Copy link
Contributor

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

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

malishav added 9 commits July 26, 2018 15:23
Assumes Authorization Server (AS) is listening on a loopback interface.
Client requests access to SCOPE resource without knowing where this
resource is located. The IPv6 address of the RS is communicated to the
client in the audience parameter of the response. Upon reception of the
response, client installs a new OSCORE context and uses it to access the
SCOPE resource on the RS.
TODO: Obtain this dynamically when first contacting the RS.
Client contacts the RS directly and obtains the URI of the AS where it
should request the access token. Exception handling needs to be
improved.
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.

1 participant