Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
OmniAuth Strategy for Constant Contact using OAuth2
Ruby
branch: master
Failed to load latest commit information.
lib Using v2 account/info endpoint to fetch account data
spec
.gitignore Initial commit
.travis.yml stop testing on ruby 1.8.7, add 2.0.0
Gemfile stop testing on ruby 1.8.7, add 2.0.0
Guardfile Initial commit
LICENSE
README.md
Rakefile Initial commit
omniauth-constantcontact2.gemspec fixed failing tests, updated to modern rspec syntax, remove an unused…

README.md

Omniauth::ConstantContact2

Build Status

This gem is an OmniAuth 2.0 Strategy for the ConstantContact API

It supports the OmniAuth REST API which uses OAuth 2.0

Many thanks to Caleb Clark for writing the original OmniAuth strategy. This builds on his work.

Installation

Add this line to your application's Gemfile:

gem 'omniauth-constantcontact2'

And then execute:

$ bundle

Or install it yourself as:

$ gem install omniauth-constantcontact2

Usage

Then integrate the strategy into your middleware:

use OmniAuth::Builder do
  provider :constantcontact, ENV['CC_KEY'], ENV['CC_SECRET']
end

In Rails, you'll want to add to the middleware stack:

Rails.application.config.middleware.use OmniAuth::Builder do
  provider :constantcontact, ENV['CC_KEY'], ENV['CC_SECRET']
end

** Ensure that you have provided the correct Redirect URI in Constant Contact when you generated the Key. You are likely to see an error stating "invalid redirect" if the Request URI does not match the one from your environment.

In development for example the Redirect URI is

http://localhost:3000/auth/constantcontact/callback

You will have to put in your consumer key and secret, which you can find at http://community.constantcontact.com/t5/Documentation/API-Keys/ba-p/25015

For additional information, refer to the OmniAuth wiki.

Contributing

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

Copyright

Copyright (c) 2012 Aditya Sanghi. See LICENSE for details.

Something went wrong with that request. Please try again.