minimalist_authentication 0.6.14 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (60) hide show
  1. checksums.yaml +4 -4
  2. data/MIT-LICENSE +1 -1
  3. data/README.md +56 -52
  4. data/Rakefile +27 -26
  5. data/{test/rails_root/lib/tasks/.gitkeep → app/assets/config/minimalist_authentication_manifest.js} +0 -0
  6. data/app/views/sessions/_form.html.erb +5 -0
  7. data/app/views/sessions/new.html.erb +1 -0
  8. data/config/routes.rb +2 -0
  9. data/lib/minimalist/authentication.rb +69 -79
  10. data/lib/minimalist/authorization.rb +30 -35
  11. data/lib/minimalist/sessions.rb +45 -49
  12. data/lib/minimalist/test_helper.rb +5 -5
  13. data/lib/minimalist_authentication.rb +3 -1
  14. data/lib/minimalist_authentication/engine.rb +4 -0
  15. data/lib/{minimalist → minimalist_authentication}/version.rb +1 -1
  16. metadata +24 -128
  17. data/.gitignore +0 -6
  18. data/Gemfile +0 -2
  19. data/Gemfile.lock +0 -101
  20. data/lib/app/views/sessions/_form.html.erb +0 -12
  21. data/lib/app/views/sessions/new.html.erb +0 -1
  22. data/minimalist_authentication.gemspec +0 -23
  23. data/test/.gitignore +0 -1
  24. data/test/authentication_test.rb +0 -103
  25. data/test/authorization_test.rb +0 -77
  26. data/test/factories.rb +0 -12
  27. data/test/jenkins.bash +0 -9
  28. data/test/rails_root/README +0 -256
  29. data/test/rails_root/Rakefile +0 -7
  30. data/test/rails_root/app/controllers/application_controller.rb +0 -5
  31. data/test/rails_root/app/controllers/sessions_controller.rb +0 -3
  32. data/test/rails_root/app/helpers/application_helper.rb +0 -2
  33. data/test/rails_root/app/models/user.rb +0 -4
  34. data/test/rails_root/app/views/layouts/application.html.erb +0 -14
  35. data/test/rails_root/config.ru +0 -4
  36. data/test/rails_root/config/application.rb +0 -42
  37. data/test/rails_root/config/boot.rb +0 -13
  38. data/test/rails_root/config/database.yml +0 -22
  39. data/test/rails_root/config/environment.rb +0 -5
  40. data/test/rails_root/config/environments/development.rb +0 -26
  41. data/test/rails_root/config/environments/production.rb +0 -49
  42. data/test/rails_root/config/environments/test.rb +0 -35
  43. data/test/rails_root/config/initializers/backtrace_silencers.rb +0 -7
  44. data/test/rails_root/config/initializers/inflections.rb +0 -10
  45. data/test/rails_root/config/initializers/mime_types.rb +0 -5
  46. data/test/rails_root/config/initializers/secret_token.rb +0 -7
  47. data/test/rails_root/config/initializers/session_store.rb +0 -8
  48. data/test/rails_root/config/locales/en.yml +0 -5
  49. data/test/rails_root/config/routes.rb +0 -5
  50. data/test/rails_root/db/.gitignore +0 -2
  51. data/test/rails_root/db/schema.rb +0 -21
  52. data/test/rails_root/db/seeds.rb +0 -7
  53. data/test/rails_root/doc/README_FOR_APP +0 -2
  54. data/test/rails_root/log/.gitignore +0 -1
  55. data/test/rails_root/log/.gitkeep +0 -0
  56. data/test/rails_root/script/rails +0 -6
  57. data/test/rails_root/test/performance/browsing_test.rb +0 -9
  58. data/test/rails_root/test/test_helper.rb +0 -13
  59. data/test/sessions_test.rb +0 -30
  60. data/test/test_helper.rb +0 -12
@@ -1,12 +0,0 @@
1
- <%= form_tag session_path do %>
2
- <div>
3
- <%= label_tag 'email' %>
4
- <%= text_field_tag 'email', @email %>
5
- </div>
6
- <div>
7
- <%= label_tag 'password' %>
8
- <%= password_field_tag 'password', nil %>
9
- </div>
10
-
11
- <p><%= submit_tag 'Log in', :class =>'submit' %></p>
12
- <% end %>
@@ -1 +0,0 @@
1
- <%= render :partial => 'form' %>
@@ -1,23 +0,0 @@
1
- require File.expand_path('../lib/minimalist/version', __FILE__)
2
-
3
- Gem::Specification.new do |s|
4
- s.name = "minimalist_authentication"
5
- s.version = MinimalistAuthentication::VERSION
6
- s.platform = Gem::Platform::RUBY
7
- s.authors = ['Aaron Baldwin', 'WWIDEA, Inc']
8
- s.email = ["developers@wwidea.org"]
9
- s.homepage = "https://github.com/wwidea/minimalist_authentication"
10
- s.summary = %q{A Rails authentication plugin that takes a minimalist approach.}
11
- 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.}
12
- s.license = 'MIT'
13
-
14
- s.files = `git ls-files`.split("\n")
15
- s.test_files = `git ls-files -- test/*`.split("\n")
16
- s.require_paths = ["lib"]
17
-
18
- s.add_dependency 'bcrypt', '~> 3.1', '>= 3.1.3'
19
-
20
- s.add_development_dependency 'rails','3.2.14'
21
- s.add_development_dependency 'sqlite3', '~> 1.3 ', '>= 1.3.9'
22
- s.add_development_dependency 'factory_girl', '~> 4.4', '>= 4.4.0'
23
- end
data/test/.gitignore DELETED
@@ -1 +0,0 @@
1
- debug.log
@@ -1,103 +0,0 @@
1
- require 'test_helper'
2
-
3
- class AuthenticationTest < ActiveSupport::TestCase
4
-
5
- test "should not be able to set crypted_password through mass assignment" do
6
- user = FactoryGirl.create(:user)
7
- old_crypted_password = user.crypted_password
8
- old_digest_version = user.using_digest_version
9
- old_salt = user.salt
10
- user.update_attributes(:crypted_password => 'should not work')
11
- assert_equal(old_digest_version, user.using_digest_version)
12
- assert_equal(old_salt, user.salt)
13
- assert_equal(old_crypted_password, user.crypted_password)
14
- end
15
-
16
- test "should return active user" do
17
- user = FactoryGirl.create(:user)
18
- assert_equal([user], User.active)
19
- end
20
-
21
- test "should authenticate user" do
22
- user = FactoryGirl.create(:user)
23
- assert_equal(user, User.authenticate(user.email, 'password'))
24
- end
25
-
26
- test "should fail to authenticate when email is blank" do
27
- user = FactoryGirl.create(:user)
28
- assert_nil(User.authenticate('', 'password'))
29
- end
30
-
31
- test "should fail to authenticate when password is blank" do
32
- user = FactoryGirl.create(:user)
33
- assert_nil(User.authenticate(user.email, ''))
34
- end
35
-
36
- test "should fail to authenticate when user is not active" do
37
- user = FactoryGirl.create(:user, :active => false)
38
- assert_nil(User.authenticate(user.email, 'password'))
39
- end
40
-
41
- test "should fail to authenticate for incorrect password" do
42
- user = FactoryGirl.create(:user)
43
- assert_nil(User.authenticate(user.email, 'incorrect_password'))
44
- end
45
-
46
- test "should create salt and encrypted_password for new user" do
47
- user = User.new(:email => 'test@testing.com', :password => 'testing')
48
- assert(user.save)
49
- assert_not_nil(user.salt)
50
- assert_not_nil(user.crypted_password)
51
- assert(user.authenticated?('testing'))
52
- end
53
-
54
- test "should update last_logged_in_at without updating updated_at timestamp" do
55
- user = FactoryGirl.create(:user, :updated_at => 1.day.ago)
56
- updated_at = user.updated_at
57
- user.logged_in
58
- assert(user.updated_at == updated_at)
59
- end
60
-
61
- test "guest should be guest" do
62
- assert(User.guest.is_guest?)
63
- end
64
-
65
- test "should allow inactive user to pass validation without an email or password" do
66
- assert(User.new.valid?)
67
- end
68
-
69
- test "should fail validation for active user without email" do
70
- user = User.new(:active => true)
71
- assert_equal(false, user.valid?)
72
- assert(user.errors[:email])
73
- end
74
-
75
- test "should fail validation for active user without password" do
76
- user = User.new(:active => true)
77
- assert_equal(false, user.valid?)
78
- assert(user.errors[:password])
79
- end
80
-
81
- test "should use latest digest version for new users" do
82
- assert_equal(User::PREFERRED_DIGEST_VERSION,FactoryGirl.create(:user).using_digest_version)
83
- end
84
-
85
- test "should migrate legacy users to new digest version" do
86
- #Setup a user using the old digest version.
87
- #This wouldn't be necessary with fixtures.
88
- legacy_user = User.create(:active => true, :email => 'legacy@user.com', :password => '123456', :password_confirmation => '123456')
89
- legacy_user.password = nil
90
- legacy_user.salt = 'my_salt'
91
- legacy_user.crypted_password = User.secure_digest('my_password', 'my_salt', 1)
92
- legacy_user.using_digest_version = nil
93
- assert(legacy_user.save)
94
- assert_equal(nil, legacy_user.reload.using_digest_version)
95
- assert_equal('86f156baf9e4868e6dcf910b65775efdeaa347d8',legacy_user.crypted_password)
96
-
97
- # Ok, now we can finally do the test.
98
- legacy_crypted_password = legacy_user.crypted_password
99
- assert(legacy_user.authenticated?('my_password'))
100
- assert_equal(Minimalist::Authentication::PREFERRED_DIGEST_VERSION,legacy_user.reload.using_digest_version)
101
- assert_not_equal(legacy_crypted_password,legacy_user.crypted_password)
102
- end
103
- end
@@ -1,77 +0,0 @@
1
- require 'test_helper'
2
-
3
- class AuthorizationTest < ActiveSupport::TestCase
4
- def AuthorizationTest.helper_method(*args); end
5
- include Minimalist::Authorization
6
-
7
- test "should return guest for current_user" do
8
- assert_equal('guest', current_user.email)
9
- end
10
-
11
- test "should return logged_in user for current_user" do
12
- user = FactoryGirl.create(:user)
13
- session[:user_id] = user.id
14
- assert_equal(user, current_user)
15
- end
16
-
17
- test "should pass authorization" do
18
- user = FactoryGirl.create(:user)
19
- session[:user_id] = user.id
20
- assert(authorization_required)
21
- end
22
-
23
- test "should fail authorization" do
24
- assert_equal(new_session_path, authorization_required)
25
- end
26
-
27
- test "should store location" do
28
- store_location
29
- assert_equal(request.fullpath, session['return_to'])
30
- end
31
-
32
- test "should redirect to stored location" do
33
- store_location
34
- redirect_back_or_default('/')
35
- assert_equal(request.fullpath, redirect_to)
36
- end
37
-
38
- test "should redirect to stored location only once" do
39
- store_location
40
- redirect_back_or_default('/')
41
- assert_equal(request.fullpath, redirect_to)
42
- redirect_back_or_default('/')
43
- assert_equal('/', redirect_to)
44
- end
45
-
46
- test "should redirect to default" do
47
- redirect_back_or_default('/')
48
- assert_equal('/', redirect_to)
49
- end
50
-
51
- #######
52
- private
53
- #######
54
-
55
- def redirect_to(path = nil)
56
- @redirect_to = path if path
57
- return @redirect_to
58
- end
59
-
60
- def session; @session ||= Hash.new; end
61
-
62
- def action_name; nil; end
63
- def controller_name; nil; end
64
- def new_session_path; '/session/new'; end
65
-
66
- def request
67
- (Class.new do
68
- def method
69
- :get
70
- end
71
-
72
- def fullpath
73
- 'http://www.example.com'
74
- end
75
- end).new
76
- end
77
- end
data/test/factories.rb DELETED
@@ -1,12 +0,0 @@
1
- module Factories
2
- salt = User.make_token
3
- FactoryGirl.define do
4
- factory :user do
5
- active true
6
- email 'test@testing.com'
7
- salt salt
8
- crypted_password User.secure_digest('password',salt,Minimalist::Authentication::PREFERRED_DIGEST_VERSION)
9
- using_digest_version Minimalist::Authentication::PREFERRED_DIGEST_VERSION
10
- end
11
- end
12
- end
data/test/jenkins.bash DELETED
@@ -1,9 +0,0 @@
1
- #!/bin/bash
2
- bundle install
3
-
4
- cd test/rails_root
5
- bundle exec rake db:setup
6
- bundle exec rake db:test:prepare
7
-
8
- cd ../../
9
- bundle exec rake test
@@ -1,256 +0,0 @@
1
- == Welcome to Rails
2
-
3
- Rails is a web-application framework that includes everything needed to create
4
- database-backed web applications according to the Model-View-Control pattern.
5
-
6
- This pattern splits the view (also called the presentation) into "dumb"
7
- templates that are primarily responsible for inserting pre-built data in between
8
- HTML tags. The model contains the "smart" domain objects (such as Account,
9
- Product, Person, Post) that holds all the business logic and knows how to
10
- persist themselves to a database. The controller handles the incoming requests
11
- (such as Save New Account, Update Product, Show Post) by manipulating the model
12
- and directing data to the view.
13
-
14
- In Rails, the model is handled by what's called an object-relational mapping
15
- layer entitled Active Record. This layer allows you to present the data from
16
- database rows as objects and embellish these data objects with business logic
17
- methods. You can read more about Active Record in
18
- link:files/vendor/rails/activerecord/README.html.
19
-
20
- The controller and view are handled by the Action Pack, which handles both
21
- layers by its two parts: Action View and Action Controller. These two layers
22
- are bundled in a single package due to their heavy interdependence. This is
23
- unlike the relationship between the Active Record and Action Pack that is much
24
- more separate. Each of these packages can be used independently outside of
25
- Rails. You can read more about Action Pack in
26
- link:files/vendor/rails/actionpack/README.html.
27
-
28
-
29
- == Getting Started
30
-
31
- 1. At the command prompt, create a new Rails application:
32
- <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
33
-
34
- 2. Change directory to <tt>myapp</tt> and start the web server:
35
- <tt>cd myapp; rails server</tt> (run with --help for options)
36
-
37
- 3. Go to http://localhost:3000/ and you'll see:
38
- "Welcome aboard: You're riding Ruby on Rails!"
39
-
40
- 4. Follow the guidelines to start developing your application. You can find
41
- the following resources handy:
42
-
43
- * The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
44
- * Ruby on Rails Tutorial Book: http://www.railstutorial.org/
45
-
46
-
47
- == Debugging Rails
48
-
49
- Sometimes your application goes wrong. Fortunately there are a lot of tools that
50
- will help you debug it and get it back on the rails.
51
-
52
- First area to check is the application log files. Have "tail -f" commands
53
- running on the server.log and development.log. Rails will automatically display
54
- debugging and runtime information to these files. Debugging info will also be
55
- shown in the browser on requests from 127.0.0.1.
56
-
57
- You can also log your own messages directly into the log file from your code
58
- using the Ruby logger class from inside your controllers. Example:
59
-
60
- class WeblogController < ActionController::Base
61
- def destroy
62
- @weblog = Weblog.find(params[:id])
63
- @weblog.destroy
64
- logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
65
- end
66
- end
67
-
68
- The result will be a message in your log file along the lines of:
69
-
70
- Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
71
-
72
- More information on how to use the logger is at http://www.ruby-doc.org/core/
73
-
74
- Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
75
- several books available online as well:
76
-
77
- * Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
78
- * Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
79
-
80
- These two books will bring you up to speed on the Ruby language and also on
81
- programming in general.
82
-
83
-
84
- == Debugger
85
-
86
- Debugger support is available through the debugger command when you start your
87
- Mongrel or WEBrick server with --debugger. This means that you can break out of
88
- execution at any point in the code, investigate and change the model, and then,
89
- resume execution! You need to install ruby-debug to run the server in debugging
90
- mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
91
-
92
- class WeblogController < ActionController::Base
93
- def index
94
- @posts = Post.find(:all)
95
- debugger
96
- end
97
- end
98
-
99
- So the controller will accept the action, run the first line, then present you
100
- with a IRB prompt in the server window. Here you can do things like:
101
-
102
- >> @posts.inspect
103
- => "[#<Post:0x14a6be8
104
- @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
105
- #<Post:0x14a6620
106
- @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
107
- >> @posts.first.title = "hello from a debugger"
108
- => "hello from a debugger"
109
-
110
- ...and even better, you can examine how your runtime objects actually work:
111
-
112
- >> f = @posts.first
113
- => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
114
- >> f.
115
- Display all 152 possibilities? (y or n)
116
-
117
- Finally, when you're ready to resume execution, you can enter "cont".
118
-
119
-
120
- == Console
121
-
122
- The console is a Ruby shell, which allows you to interact with your
123
- application's domain model. Here you'll have all parts of the application
124
- configured, just like it is when the application is running. You can inspect
125
- domain models, change values, and save to the database. Starting the script
126
- without arguments will launch it in the development environment.
127
-
128
- To start the console, run <tt>rails console</tt> from the application
129
- directory.
130
-
131
- Options:
132
-
133
- * Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
134
- made to the database.
135
- * Passing an environment name as an argument will load the corresponding
136
- environment. Example: <tt>rails console production</tt>.
137
-
138
- To reload your controllers and models after launching the console run
139
- <tt>reload!</tt>
140
-
141
- More information about irb can be found at:
142
- link:http://www.rubycentral.com/pickaxe/irb.html
143
-
144
-
145
- == dbconsole
146
-
147
- You can go to the command line of your database directly through <tt>rails
148
- dbconsole</tt>. You would be connected to the database with the credentials
149
- defined in database.yml. Starting the script without arguments will connect you
150
- to the development database. Passing an argument will connect you to a different
151
- database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
152
- PostgreSQL and SQLite 3.
153
-
154
- == Description of Contents
155
-
156
- The default directory structure of a generated Ruby on Rails application:
157
-
158
- |-- app
159
- | |-- controllers
160
- | |-- helpers
161
- | |-- mailers
162
- | |-- models
163
- | `-- views
164
- | `-- layouts
165
- |-- config
166
- | |-- environments
167
- | |-- initializers
168
- | `-- locales
169
- |-- db
170
- |-- doc
171
- |-- lib
172
- | `-- tasks
173
- |-- log
174
- |-- public
175
- | |-- images
176
- | |-- javascripts
177
- | `-- stylesheets
178
- |-- script
179
- |-- test
180
- | |-- fixtures
181
- | |-- functional
182
- | |-- integration
183
- | |-- performance
184
- | `-- unit
185
- |-- tmp
186
- | |-- cache
187
- | |-- pids
188
- | |-- sessions
189
- | `-- sockets
190
- `-- vendor
191
- `-- plugins
192
-
193
- app
194
- Holds all the code that's specific to this particular application.
195
-
196
- app/controllers
197
- Holds controllers that should be named like weblogs_controller.rb for
198
- automated URL mapping. All controllers should descend from
199
- ApplicationController which itself descends from ActionController::Base.
200
-
201
- app/models
202
- Holds models that should be named like post.rb. Models descend from
203
- ActiveRecord::Base by default.
204
-
205
- app/views
206
- Holds the template files for the view that should be named like
207
- weblogs/index.html.erb for the WeblogsController#index action. All views use
208
- eRuby syntax by default.
209
-
210
- app/views/layouts
211
- Holds the template files for layouts to be used with views. This models the
212
- common header/footer method of wrapping views. In your views, define a layout
213
- using the <tt>layout :default</tt> and create a file named default.html.erb.
214
- Inside default.html.erb, call <% yield %> to render the view using this
215
- layout.
216
-
217
- app/helpers
218
- Holds view helpers that should be named like weblogs_helper.rb. These are
219
- generated for you automatically when using generators for controllers.
220
- Helpers can be used to wrap functionality for your views into methods.
221
-
222
- config
223
- Configuration files for the Rails environment, the routing map, the database,
224
- and other dependencies.
225
-
226
- db
227
- Contains the database schema in schema.rb. db/migrate contains all the
228
- sequence of Migrations for your schema.
229
-
230
- doc
231
- This directory is where your application documentation will be stored when
232
- generated using <tt>rake doc:app</tt>
233
-
234
- lib
235
- Application specific libraries. Basically, any kind of custom code that
236
- doesn't belong under controllers, models, or helpers. This directory is in
237
- the load path.
238
-
239
- public
240
- The directory available for the web server. Contains subdirectories for
241
- images, stylesheets, and javascripts. Also contains the dispatchers and the
242
- default HTML files. This should be set as the DOCUMENT_ROOT of your web
243
- server.
244
-
245
- script
246
- Helper scripts for automation and generation.
247
-
248
- test
249
- Unit and functional tests along with fixtures. When using the rails generate
250
- command, template test files will be generated for you and placed in this
251
- directory.
252
-
253
- vendor
254
- External libraries that the application depends on. Also includes the plugins
255
- subdirectory. If the app has frozen rails, those gems also go here, under
256
- vendor/rails/. This directory is in the load path.