0.0
No commit activity in last 3 years
No release in over 3 years
Official OmniAuth strategy for Do (do.com).
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

Runtime

 Project Readme

OmniAuth Do

This is an OmniAuth strategy for authenticating to Do. To use it, you'll need to request an OAuth2 Application ID and Secret by e-mailing operations@do.com.

Basic Usage

use OmniAuth::Builder do
  provider :do, ENV['DO_KEY'], ENV['DO_SECRET']
end

User Scopes

Do lets you set scopes to provide granular access to different portions of a user's data. Note that during the Do API Beta period, all scopes will result in full-access to user data.

use OmniAuth::Builder do
  provider :do, ENV['DO_KEY'], ENV['DO_SECRET'], scope: "user.profile"
end

For questions about the forthcoming implementations of scopes, e-mail operations@do.com

Provisioning

In addition to accessing user data, confidential clients can utilize Do's User and Group Provisioning API's, allowed by the user.provisioning and group.provisioning scopes respectively.

Beta

The use of the Do API is subject to the terms and conditions found at do.com/legal. Take care to note Section 8.4:

Any Non-GA Services will be clearly designated as beta, pilot, limited release, developer preview, non-production or by a description of similar import. Non-GA Services are provided for evaluation purposes and not for production use, are not supported, may contain bugs or errors, and may be subject to additional terms. NON-GA SERVICES ARE NOT CONSIDERED "SERVICES" HEREUNDER AND ARE PROVIDED "AS IS" WITH NO EXPRESS OR IMPLIED WARRANTY. We may discontinue Non-GA Services at any time in Our sole discretion and may never make them generally available.

Contributions

Patches and bug reports are welcome. Just send a pull request or file an issue. Project changelog.

License