Nice Philanthropist Metalhead
Learn about our RFC process, Open RFC meetings & more.Join in the discussion! »


0.0.4 • Public • Published


CDIF's OAuth implementation

Notes to OAuth support in CDIF

This module provides OAuth authentication flow and API support to web services which can be modelled by CDIF. Because CDIF provided a common API abstraction for physical hardware or abstract service API, and also JSON schema based data integrity. We hope by introducing this module, CDIF can both flexibly and more securely model any OAuth based web services which are providing their services through web APIs for third party access.

Clients which are trying to access the API of OAuth based virtual devices managed by CDIF, such as a twitter device, must first complete the OAuth authentication flow starting from CDIF's connect framework API interface. During the connecting process, CDIF's connect framework API interface would return a url_redirect object to help client redirect to OAuth provider's authentication page and prompt user for acess granting. Successful completion of OAuth flow through CDIF's connect interface means user granted access to CDIF and its authenticated clients to access contents in its user account. CDIF would cache the acquired OAuth access token in connected device object for later on web service API calls.

For now only OAuth 1.0 and basic Twitter APIs are included in this implementation. Support to OAuth 2.0 and other web services shall be added soon.

See following links for more details:

Common device interconnect framework

OAuth Node.js library



npm i cdif-oauth-manager

DownloadsWeekly Downloads






Last publish


  • avatar