diff --git a/.travis.yml b/.travis.yml
index c033aa11..0bc81148 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,5 +1,4 @@
 rvm:
-  - 2.0.0
   - 2.3.1
   - 2.3.3
 notifications:
diff --git a/README.md b/README.md
index afeffeea..ca3cdef5 100644
--- a/README.md
+++ b/README.md
@@ -209,7 +209,7 @@ end
 To generate the SAML Response it uses a default X.509 certificate and secret key... which isn't so secret.
 You can find them in `SamlIdp::Default`. The X.509 certificate is valid until year 2032.
 Obviously you shouldn't use these if you intend to use this in production environments. In that case,
-within the controller set the properties `x509_certificate` and `secret_key` using a `prepend_before_filter`
+within the controller set the properties `x509_certificate` and `secret_key` using a `prepend_before_action`
 callback within the current request context or set them globally via the `SamlIdp.config.x509_certificate`
 and `SamlIdp.config.secret_key` properties.
 
diff --git a/app/controllers/saml_idp/idp_controller.rb b/app/controllers/saml_idp/idp_controller.rb
index a7dea911..a5300407 100644
--- a/app/controllers/saml_idp/idp_controller.rb
+++ b/app/controllers/saml_idp/idp_controller.rb
@@ -5,7 +5,7 @@ class IdpController < ActionController::Base
 
     unloadable unless Rails::VERSION::MAJOR >= 4
     protect_from_forgery
-    before_filter :validate_saml_request, only: [:new, :create]
+    before_action :validate_saml_request, only: [:new, :create]
 
     def new
       render template: "saml_idp/idp/new"
diff --git a/lib/saml_idp/version.rb b/lib/saml_idp/version.rb
index f0aa579a..9d418e1a 100644
--- a/lib/saml_idp/version.rb
+++ b/lib/saml_idp/version.rb
@@ -1,4 +1,4 @@
 # encoding: utf-8
 module SamlIdp
-  VERSION = '0.4.0'
+  VERSION = '0.4.3-18f'
 end