duo_security 0.0.1

data/.gitignore

@@ -0,0 +1,12 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+doc/
+lib/bundler/man
+pkg
+rdoc
+tmp
+fixtures/vcr/*

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in duo_security.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2012 Marten Veldthuis
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,36 @@
+# DuoSecurity
+
+This gem provides an API for integrating with DuoSecurity's two-factor
+authentication system. It also comes with a shell script that allows you to
+plug this into other systems, for example a FreeRadius server.
+
+## Installation
+
+    $ gem install duo_security
+
+## Usage
+
+The shell scripts depend upon three environment variables being set:
+
+    DUO_HOST=api-XXXXXXXX.duosecurity.com
+    DUO_SKEY=your_secret_key
+    DUO_IKEY=your_integration_key
+
+## Contributing
+
+Running the tests also depends upon the above three environment variables to be
+set to an account of your choosing. Running the tests performs actual requests
+to the account, although for the sake of speed they are cached in the
+`fixtures/vcr` folder after the first run. 
+
+When performing actual requests, the tests will tell you what you action you
+need to take in the mobile application for the test case that's being executed
+(e.g. approve).
+
+The following workflow is advised:
+
+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

data/Rakefile

@@ -0,0 +1,9 @@
+#!/usr/bin/env rake
+require "bundler/gem_tasks"
+require 'rake/testtask'
+
+Rake::TestTask.new do |t|
+  t.pattern = "spec/**/*_spec.rb"
+end
+
+task :default => :test

data/bin/duo

@@ -0,0 +1,20 @@
+#!/usr/bin/env ruby
+
+require 'duo_security'
+
+host = ENV.fetch("DUO_HOST")
+skey = ENV.fetch("DUO_SKEY")
+ikey = ENV.fetch("DUO_IKEY")
+user = ARGV[0]
+
+api = DuoSecurity::API.new(host, skey, ikey)
+attempt = DuoSecurity::Attempt.new(api, user).login!
+
+if attempt == true
+  puts "Successful login for #{user}"
+  exit 0
+end
+
+# Fall back to failure
+puts "Failed login attempt for #{user}"
+exit 1