Fork me on GitHub
Learn more at the sources:



This guide will give you an introduction to the security features included in ruby on rails, how to use them, and how to mess up in spite of all the help the framework is giving you

By referring to this guide, you will be able to:

  • Use rails's security features
  • Appreciate how hard security is

  • rewrite example test for minitest

You can fork the code of the example app. his app is full of security holes. While reading this guide you should work on the app and fix those holes one by one.

1 Don't display confidential data

Rails offers a lot of security features. But all those clever features cannot save you from yourself. In the example app all the passwords are displayed on "/users". No framework can prevent that!

Let's use this as an example of how to fix a security problem once you've found it: First we write a test for the problem: rails g integration_test users

require 'test_helper'

class UsersTest < ActionDispatch::IntegrationTest
  fixtures :users

  test 'users are listed publicly' do
    get '/users'
    assert_response :success
    assert_select 'td', users(:one).email

  test 'users passwords are not shown publicly' do
    get '/users'
    assert_response :success
    assert_select 'td', { text: users(:one).password, count: 0 }, 'no table cell contains a password'

When we run this test it fails, because right now passwords are displayed:

Now we change the view to not display the passwords any more. We can run the test to make sure we succeeded.

2 See Also