On Thu, Aug 9, 2018, 1:25 PM Ondrej Tomcik
<ondrej.tom...@kistler.com<mailto:ondrej.tom...@kistler.com>> wrote:
On Thu, Aug 9, 2018, 6:48 AM Ondrej Tomcik
<ondrej.tom...@kistler.com<mailto:ondrej.tom...@kistler.com>> wrote:
Dear IoTivity devs,
Please be informed that the new Cloud 2.0 design concept is alive:
https://wiki.iotivity.org/coapnativecloud
Your comments are warmly welcome.
Btw, I applaud your efforts, please take my feedback positively.
Think you need to align some language with the OAuth spec. E.g. "authorization
code" is a technical term with specific semantics in OAuth 2, not sure how
you're using it.
I am referring exactly to the "authorization code" from the OAuth2 terminology.
Ok. The implication is that that is the only supported grant type. Is that the
case?
It is the only supported grant type for the device onboarding - sign up. It's
in the specification, but they didn't explicitly say that it's the OAuth2.
1. User will ask the OAuth Server to issue the authorization code
2. Authorization code is through the provisioning tool set to the cloud
resource on the device, together with the IP, etc.
3. Device will connect and proceed with sign-up -> send the authorization
code to the OCF Native Cloud
4. OCF Native Cloud will exchange authorization code for the access token
(with OAuth Server)
5. Access token is returned to the device and the device is authorized
For this process, authorization code grant type is required.
Implementation is in progress.
BR
Ondrej Tomcik :: KISTLER :: measure, analyze, inovate
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9847):
https://lists.iotivity.org/g/iotivity-dev/message/9847
Mute This Topic: https://lists.iotivity.org/mt/24238274/21656
Group Owner: iotivity-dev+ow...@lists.iotivity.org
Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
