minimalist_authentication 0.6.14 → 1.0.0

data/lib/app/views/sessions/_form.html.erb

@@ -1,12 +0,0 @@
-<%= form_tag session_path do %>
-  <div>
-    <%= label_tag 'email' %>
-    <%= text_field_tag 'email', @email %>
-  </div>
-  <div>
-    <%= label_tag 'password' %>
-    <%= password_field_tag 'password', nil %>
-  </div>
-
-  <p><%= submit_tag 'Log in', :class =>'submit' %></p>
-<% end %>

data/lib/app/views/sessions/new.html.erb

@@ -1 +0,0 @@
-<%= render :partial => 'form' %>

data/minimalist_authentication.gemspec

@@ -1,23 +0,0 @@
-require File.expand_path('../lib/minimalist/version', __FILE__)
-
-Gem::Specification.new do |s|
-  s.name          = "minimalist_authentication"
-  s.version       = MinimalistAuthentication::VERSION
-  s.platform      = Gem::Platform::RUBY
-  s.authors       = ['Aaron Baldwin', 'WWIDEA, Inc']
-  s.email         = ["developers@wwidea.org"]
-  s.homepage      = "https://github.com/wwidea/minimalist_authentication"
-  s.summary       = %q{A Rails authentication plugin that takes a minimalist approach.}
-  s.description   = %q{A Rails authentication plugin that takes a minimalist approach. It is designed to be simple to understand, use, and modify for your application.}
-  s.license       = 'MIT'
-  
-  s.files         = `git ls-files`.split("\n")
-  s.test_files    = `git ls-files -- test/*`.split("\n")
-  s.require_paths = ["lib"]
-  
-  s.add_dependency 'bcrypt', '~> 3.1', '>= 3.1.3'
-  
-  s.add_development_dependency  'rails','3.2.14'
-  s.add_development_dependency  'sqlite3', '~> 1.3 ', '>= 1.3.9'
-  s.add_development_dependency  'factory_girl', '~> 4.4', '>= 4.4.0'
-end

data/test/.gitignore

@@ -1 +0,0 @@
-debug.log

data/test/authentication_test.rb

@@ -1,103 +0,0 @@
-require 'test_helper'
-
-class AuthenticationTest < ActiveSupport::TestCase
-
-  test "should not be able to set crypted_password through mass assignment" do
-    user = FactoryGirl.create(:user)
-    old_crypted_password = user.crypted_password
-    old_digest_version = user.using_digest_version
-    old_salt = user.salt
-    user.update_attributes(:crypted_password => 'should not work')
-    assert_equal(old_digest_version, user.using_digest_version)
-    assert_equal(old_salt, user.salt)
-    assert_equal(old_crypted_password, user.crypted_password)
-  end
-
-  test "should return active user" do
-    user = FactoryGirl.create(:user)
-    assert_equal([user], User.active)
-  end
-
-  test "should authenticate user" do
-    user = FactoryGirl.create(:user)
-    assert_equal(user, User.authenticate(user.email, 'password'))
-  end
-
-  test "should fail to authenticate when email is blank" do
-    user = FactoryGirl.create(:user)
-    assert_nil(User.authenticate('', 'password'))
-  end
-
-  test "should fail to authenticate when password is blank" do
-    user = FactoryGirl.create(:user)
-    assert_nil(User.authenticate(user.email, ''))
-  end
-
-  test "should fail to authenticate when user is not active" do
-    user = FactoryGirl.create(:user, :active => false)
-    assert_nil(User.authenticate(user.email, 'password'))
-  end
-
-  test "should fail to authenticate for incorrect password" do
-    user = FactoryGirl.create(:user)
-    assert_nil(User.authenticate(user.email, 'incorrect_password'))
-  end
-
-  test "should create salt and encrypted_password for new user" do
-    user = User.new(:email => 'test@testing.com', :password => 'testing')
-    assert(user.save)
-    assert_not_nil(user.salt)
-    assert_not_nil(user.crypted_password)
-    assert(user.authenticated?('testing'))
-  end
-
-  test "should update last_logged_in_at without updating updated_at timestamp" do
-    user = FactoryGirl.create(:user, :updated_at => 1.day.ago)
-    updated_at = user.updated_at
-    user.logged_in
-    assert(user.updated_at == updated_at)
-  end
-
-  test "guest should be guest" do
-    assert(User.guest.is_guest?)
-  end
-
-  test "should allow inactive user to pass validation without an email or password" do
-    assert(User.new.valid?)
-  end
-
-  test "should fail validation for active user without email" do
-    user = User.new(:active => true)
-    assert_equal(false, user.valid?)
-    assert(user.errors[:email])
-  end
-
-  test "should fail validation for active user without password" do
-    user = User.new(:active => true)
-    assert_equal(false, user.valid?)
-    assert(user.errors[:password])
-  end
-
-  test "should use latest digest version for new users" do
-    assert_equal(User::PREFERRED_DIGEST_VERSION,FactoryGirl.create(:user).using_digest_version)
-  end
-
-  test "should migrate legacy users to new digest version" do
-    #Setup a user using the old digest version.
-    #This wouldn't be necessary with fixtures.
-    legacy_user = User.create(:active => true, :email => 'legacy@user.com', :password => '123456', :password_confirmation => '123456')
-    legacy_user.password = nil
-    legacy_user.salt = 'my_salt'
-    legacy_user.crypted_password = User.secure_digest('my_password', 'my_salt', 1)
-    legacy_user.using_digest_version = nil
-    assert(legacy_user.save)
-    assert_equal(nil, legacy_user.reload.using_digest_version)
-    assert_equal('86f156baf9e4868e6dcf910b65775efdeaa347d8',legacy_user.crypted_password)
-
-    # Ok, now we can finally do the test.
-    legacy_crypted_password = legacy_user.crypted_password
-    assert(legacy_user.authenticated?('my_password'))
-    assert_equal(Minimalist::Authentication::PREFERRED_DIGEST_VERSION,legacy_user.reload.using_digest_version)
-    assert_not_equal(legacy_crypted_password,legacy_user.crypted_password)
-  end
-end

data/test/authorization_test.rb

@@ -1,77 +0,0 @@
-require 'test_helper'
-
-class AuthorizationTest < ActiveSupport::TestCase
-  def AuthorizationTest.helper_method(*args); end
-  include Minimalist::Authorization
-
-  test "should return guest for current_user" do
-    assert_equal('guest', current_user.email)
-  end
-
-  test "should return logged_in user for current_user" do
-    user = FactoryGirl.create(:user)
-    session[:user_id] = user.id
-    assert_equal(user, current_user)
-  end
-
-  test "should pass authorization" do
-    user = FactoryGirl.create(:user)
-    session[:user_id] = user.id
-    assert(authorization_required)
-  end
-
-  test "should fail authorization" do
-    assert_equal(new_session_path, authorization_required)
-  end
-
-  test "should store location" do
-    store_location
-    assert_equal(request.fullpath, session['return_to'])
-  end
-
-  test "should redirect to stored location" do
-    store_location
-    redirect_back_or_default('/')
-    assert_equal(request.fullpath, redirect_to)
-  end
-
-  test "should redirect to stored location only once" do
-    store_location
-    redirect_back_or_default('/')
-    assert_equal(request.fullpath, redirect_to)
-    redirect_back_or_default('/')
-    assert_equal('/', redirect_to)
-  end
-
-  test "should redirect to default" do
-    redirect_back_or_default('/')
-    assert_equal('/', redirect_to)
-  end
-
-  #######
-  private
-  #######
-
-  def redirect_to(path = nil)
-    @redirect_to = path if path
-    return @redirect_to
-  end
-
-  def session; @session ||= Hash.new; end
-
-  def action_name; nil; end
-  def controller_name; nil; end
-  def new_session_path; '/session/new'; end
-
-  def request
-    (Class.new do
-      def method
-        :get
-      end
-
-      def fullpath
-        'http://www.example.com'
-      end
-    end).new
-  end
-end

data/test/factories.rb

@@ -1,12 +0,0 @@
-module Factories
-  salt = User.make_token
-  FactoryGirl.define do
-    factory :user do
-      active true
-      email 'test@testing.com'
-      salt salt
-      crypted_password User.secure_digest('password',salt,Minimalist::Authentication::PREFERRED_DIGEST_VERSION)
-      using_digest_version Minimalist::Authentication::PREFERRED_DIGEST_VERSION
-    end
-  end
-end

data/test/jenkins.bash

@@ -1,9 +0,0 @@
-#!/bin/bash
-bundle install
-
-cd test/rails_root
-bundle exec rake db:setup
-bundle exec rake db:test:prepare
-
-cd ../../
-bundle exec rake test

data/test/rails_root/README

@@ -1,256 +0,0 @@
-== Welcome to Rails
-
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
-
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
-
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-
-
-== Getting Started
-
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
-
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
-
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
-
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
-
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
-
-
-== Debugging Rails
-
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.find(:all)
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better, you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you can enter "cont".
-
-
-== Console
-
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-
-To start the console, run <tt>rails console</tt> from the application
-directory.
-
-Options:
-
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-
-More information about irb can be found at:
-link:http://www.rubycentral.com/pickaxe/irb.html
-
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-
-== Description of Contents
-
-The default directory structure of a generated Ruby on Rails application:
-
-  |-- app
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |   |-- images
-  |   |-- javascripts
-  |   `-- stylesheets
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-
-public
-  The directory available for the web server. Contains subdirectories for
-  images, stylesheets, and javascripts. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.