No release in over a year
Dexcom OAuth2 strategy for OmniAuth.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 1.16, < 3.0
~> 12.3
~> 3.6
~> 0.16

Runtime

 Project Readme

OmniAuth Dexcom OAuth2 Strategy

Build Status Gem Version

A Dexcom OAuth2 strategy for OmniAuth.

For more details, read the Dexcom documentation

Installation

Add this line to your application's Gemfile:

gem 'omniauth-dexcom-oauth2'

And then execute:

$ bundle

Or install it yourself as:

$ gem install omniauth-dexcom-oauth2

Usage

Register your application with dexcom to receive an API key: https://developer.dexcom.com/

This is an example that you might put into a Rails initializer at config/initializers/omniauth.rb:

Rails.application.config.middleware.use OmniAuth::Builder do
  provider :dexcom, ENV['DEXCOM_CLIENT_ID'], ENV['DEXCOM_CLIENT_SECRET'], :scope => 'offline_access'
end

You can now access the OmniAuth Dexcom OAuth2 URL: /auth/dexcom.

Granting Member Permissions to Your Application

With the Dexcom API, you have the ability to specify which permissions you want users to grant your application. For more details, read the Dexcom documentation

The five scopes of data access:

  • Estimated Blood Glucose Levels
  • Calibration Data
  • Events Entry Data
  • Device Details
  • CGM Statistics

You can configure the scope option:

provider :dexcom, ENV['DEXCOM_CLIENT_ID'], ENV['DEXCOM_CLIENT_SECRET'], :scope => 'offline_access'

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request