`

devise:用于rails的验证 (一)

 
阅读更多
1、新建rails工程
  $ rails new app1 -d=mysql

配置Gemfile文件,添加一句:
gem 'devise'             #devise是一个gem包

  $ bundle install

解释:
devise是一个开源的工程,主要用于用户的注册、登录、找回密码、session等等。
所谓“不要重复制造轮子”,既然有好的工程,我们就拿来用,直接在Gemfile中作为
gem包引入,方便之极。Do you want to know more?
https://github.com/plataformatec/devise

2、配置devise『所有有管登录,注册,撤销 的 controllers、view、helper 都有了,在插件devise目录里
(1)应用devise:
  $ rails g devise:install
  
=========== 输出如下: =========================
Some setup you must do manually if you haven't yet:
  1. Setup default url options for your specific environment. Here is an
     example of development environment:
     
     config.action_mailer.default_url_options = { :host => 'localhost:3000' }
     
     This is a required Rails configuration. In production it must be the
     actual host of your application
 
  2. Ensure you have defined root_url to *something* in your config/routes.rb.
     For example:
 
       root :to => "home#index"
 
  3. Ensure you have flash messages in app/views/layouts/application.html.erb.
     For example:
 
       <p class="notice"><%= notice %></p>
       <p class="alert"><%= alert %></p>
===============================================================================

(2)使用devise创建user model:
    $ rails g devise User 
在app/models文件夹下产生了一个user.rb,也就是创建了一个user model
在db/migrate文件夹下产生了一个migrate文件
在config/routes.rb文件中添加了一行 devise_for :users

(3)配置user
编辑app/models/user.rb文件
class User < ActiveRecord::Base
  # Include default devise modules. Others available are:
  # :token_authenticatable, :encryptable, :confirmable, :lockable, :timeoutable and :omniauthable
  devise :database_authenticatable, :registerable,
         :recoverable, :rememberable, :trackable, :validatable,     #末尾添加,号
         :confirmable, :lockable                 #添加这一行
 
  # Setup accessible (or protected) attributes for your model
  attr_accessible :email, :password, :password_confirmation, :remember_me
end

编辑db/migrate/20110726xxxxxx_devise_create_users.rb文件

class DeviseCreateUsers < ActiveRecord::Migration
  def self.up
    create_table(:users) do |t|
      t.database_authenticatable :null => false
      t.recoverable
      t.rememberable
      t.trackable
      #添加以下两行
      t.confirmable
      t.lockable :lock_strategy => :failed_attempts, :unlock_strategy => :both
 
      # t.encryptable
      # t.confirmable
      # t.lockable :lock_strategy => :failed_attempts, :unlock_strategy => :both
      # t.token_authenticatable
 
 
      t.timestamps
    end
 
    add_index :users, :email,                :unique => true
    add_index :users, :reset_password_token, :unique => true
    #添加以下两行
    add_index :users, :confirmation_token,   :unique => true
    add_index :users, :unlock_token,         :unique => true
    # add_index :users, :confirmation_token,   :unique => true
    # add_index :users, :unlock_token,         :unique => true
    # add_index :users, :authentication_token, :unique => true
  end
 
  def self.down
    drop_table :users
  end
end
生成数据表:
$ rake db:migrate

(3)配置邮件服务器
编辑config/initializers/devise.rb
===================================================================
# Use this hook to configure devise mailer, warden hooks and so forth. The first
# four configuration values can also be set straight in your models.
Devise.setup do |config|
  # ==> Mailer Configuration
  # Configure the e-mail address which will be shown in DeviseMailer.
  config.mailer_sender = "xxx@126.com"   #换成你的邮箱,最好不要是gmail
 
  # Configure the class responsible to send e-mails.
  # config.mailer = "Devise::Mailer"
 
  # ==> ORM configuration
  # Load and configure the ORM. Supports :active_record (default) and
  # :mongoid (bson_ext recommended) by default. Other ORMs may be
  # available as additional gems.
  require 'devise/orm/active_record'
 
  # ==> Configuration for any authentication mechanism
  # Configure which keys are used when authenticating a user. The default is
  # just :email. You can configure it to use [:username, :subdomain], so for
  # authenticating a user, both parameters are required. Remember that those
  # parameters are used only when authenticating and not when retrieving from
  # session. If you need permissions, you should implement that in a before filter.
  # You can also supply a hash where the value is a boolean determining whether
  # or not authentication should be aborted when the value is not present.
  # config.authentication_keys = [ :email ]
 
  # Configure parameters from the request object used for authentication. Each entry
  # given should be a request method and it will automatically be passed to the
  # find_for_authentication method and considered in your model lookup. For instance,
  # if you set :request_keys to [:subdomain], :subdomain will be used on authentication.
  # The same considerations mentioned for authentication_keys also apply to request_keys.
  # config.request_keys = []
 
  # Configure which authentication keys should be case-insensitive.
  # These keys will be downcased upon creating or modifying a user and when used
  # to authenticate or find a user. Default is :email.
  config.case_insensitive_keys = [ :email ]
   
  # Configure which authentication keys should have whitespace stripped.
  # These keys will have whitespace before and after removed upon creating or
  # modifying a user and when used to authenticate or find a user. Default is :email.
  config.strip_whitespace_keys = [ :email ]
 
  # Tell if authentication through request.params is enabled. True by default.
  # config.params_authenticatable = true
 
  # Tell if authentication through HTTP Basic Auth is enabled. False by default.
  # config.http_authenticatable = false
 
  # If http headers should be returned for AJAX requests. True by default.
  # config.http_authenticatable_on_xhr = true
 
  # The realm used in Http Basic Authentication. "Application" by default.
  # config.http_authentication_realm = "Application"
 
  # It will change confirmation, password recovery and other workflows
  # to behave the same regardless if the e-mail provided was right or wrong.
  # Does not affect registerable.
  # config.paranoid = true
 
  # ==> Configuration for :database_authenticatable
  # For bcrypt, this is the cost for hashing the password and defaults to 10. If
  # using other encryptors, it sets how many times you want the password re-encrypted.
  config.stretches = 10
 
  # Setup a pepper to generate the encrypted password.
  # config.pepper = "aea9dd80b922e95ec0dc3b1da7ad3068bae5b95b5d1a0cb3c9384f6dcdfdb5ca057f43ad66e191613804
d79d155c910642510991306f7c7bee8902ca6b980850"
 
  # ==> Configuration for :confirmable
  # The time you want to give your user to confirm his account. During this time
  # he will be able to access your application without confirming. Default is 0.days
  # When confirm_within is zero, the user won't be able to sign in without confirming.
  # You can use this to let your user access some features of your application
  # without confirming the account, but blocking it after a certain period
  # (ie 2 days).
  # config.confirm_within = 2.days
 
  # Defines which key will be used when confirming an account
  # config.confirmation_keys = [ :email ]
 
  # ==> Configuration for :rememberable
  # The time the user will be remembered without asking for credentials again.
  # config.remember_for = 2.weeks
 
  # If true, a valid remember token can be re-used between multiple browsers.
  # config.remember_across_browsers = true
 
  # If true, extends the user's remember period when remembered via cookie.
  # config.extend_remember_period = false
 
  # If true, uses the password salt as remember token. This should be turned
  # to false if you are not using database authenticatable.
  config.use_salt_as_remember_token = true
 
  # Options to be passed to the created cookie. For instance, you can set
  # :secure => true in order to force SSL only cookies.
  # config.cookie_options = {}
 
  # ==> Configuration for :validatable
  # Range for password length. Default is 6..128.
  # config.password_length = 6..128
 
  # Regex to use to validate the email address
  # config.email_regexp = /\A([\w\.%\+\-]+)@([\w\-]+\.)+([\w]{2,})\z/i
 
  # ==> Configuration for :timeoutable
  # The time you want to timeout the user session without activity. After this
  # time the user will be asked for credentials again. Default is 30 minutes.
  # config.timeout_in = 30.minutes
 
  # ==> Configuration for :lockable
  # Defines which strategy will be used to lock an account.
  # :failed_attempts = Locks an account after a number of failed attempts to sign in.
  # :none            = No lock strategy. You should handle locking by yourself.
  # config.lock_strategy = :failed_attempts
 
  # Defines which key will be used when locking and unlocking an account
  # config.unlock_keys = [ :email ]
 
  # Defines which strategy will be used to unlock an account.
  # :email = Sends an unlock link to the user email
  # :time  = Re-enables login after a certain amount of time (see :unlock_in below)
  # :both  = Enables both strategies
  # :none  = No unlock strategy. You should handle unlocking by yourself.
  # config.unlock_strategy = :both
 
  # Number of authentication tries before locking an account if lock_strategy
  # is failed attempts.
  # config.maximum_attempts = 20
 
  # Time interval to unlock the account if :time is enabled as unlock_strategy.
  # config.unlock_in = 1.hour
 
  # ==> Configuration for :recoverable
  #
  # Defines which key will be used when recovering the password for an account
  # config.reset_password_keys = [ :email ]
 
  # Time interval you can reset your password with a reset password key.
  # Don't put a too small interval or your users won't have the time to
  # change their passwords.
  config.reset_password_within = 2.hours
 
  # ==> Configuration for :encryptable
  # Allow you to use another encryption algorithm besides bcrypt (default). You can use
  # :sha1, :sha512 or encryptors from others authentication tools as :clearance_sha1,
  # :authlogic_sha512 (then you should set stretches above to 20 for default behavior)
  # and :restful_authentication_sha1 (then you should set stretches to 10, and copy
  # REST_AUTH_SITE_KEY to pepper)
  # config.encryptor = :sha512
 
  # ==> Configuration for :token_authenticatable
  # Defines name of the authentication token params key
  # config.token_authentication_key = :auth_token
 
  # If true, authentication through token does not store user in session and needs
  # to be supplied on each request. Useful if you are using the token as API token.
  # config.stateless_token = false
 
  # ==> Scopes configuration
  # Turn scoped views on. Before rendering "sessions/new", it will first check for
  # "users/sessions/new". It's turned off by default because it's slower if you
  # are using only default views.
  # config.scoped_views = false
 
  # Configure the default scope given to Warden. By default it's the first
  # devise role declared in your routes (usually :user).
  # config.default_scope = :user
 
  # Configure sign_out behavior.
  # Sign_out action can be scoped (i.e. /users/sign_out affects only :user scope).
  # The default is true, which means any logout action will sign out all active scopes.
  # config.sign_out_all_scopes = true
 
  # ==> Navigation configuration
  # Lists the formats that should be treated as navigational. Formats like
  # :html, should redirect to the sign in page when the user does not have
  # access, but formats like :xml or :json, should return 401.
  #
  # If you have any extra navigational formats, like :iphone or :mobile, you
  # should add them to the navigational formats lists.
  #
  # The :"*/*" and "*/*" formats below is required to match Internet
  # Explorer requests.
  # config.navigational_formats = [:"*/*", "*/*", :html]
 
  # The default HTTP method used to sign out a resource. Default is :delete.
  config.sign_out_via = :delete
 
  # ==> OmniAuth
  # Add a new OmniAuth provider. Check the wiki for more information on setting
  # up on your models and hooks.
  # config.omniauth :github, 'APP_ID', 'APP_SECRET', :scope => 'user,public_repo'
 
  # ==> Warden configuration
  # If you want to use other strategies, that are not supported by Devise, or
  # change the failure app, you can configure them inside the config.warden block.
  #
  # config.warden do |manager|
  #   manager.failure_app   = AnotherApp
  #   manager.intercept_401 = false
  #   manager.default_strategies(:scope => :user).unshift :some_external_strategy
  # end
end
================================================================
编辑config/environments/development.rb
===============================================================
R2::Application.configure do
  # Settings specified here will take precedence over those in config/application.rb
 
  # In the development environment your application's code is reloaded on
  # every request.  This slows down response time but is perfect for development
  # since you don't have to restart the webserver when you make code changes.
  config.cache_classes = false
 
  # Log error messages when you accidentally call methods on nil.
  config.whiny_nils = true
 
  # Show full error reports and disable caching
  config.consider_all_requests_local       = true
  config.action_view.debug_rjs             = true
  config.action_controller.perform_caching = false
 
  # Don't care if the mailer can't send
  config.action_mailer.raise_delivery_errors = true  #此处改为true
  #添加以下内容
  config.action_mailer.default_url_options = { :host => "localhost:3000" } #刚才devise的提示中提到这一句
  config.action_mailer.delivery_method = :smtp
  config.action_mailer.smtp_settings = {
    :address => "smtp.126.com",
    :port => 25,
    :domain => "126.com",
    :authentication => :login,
    :user_name => "xxx@126.com", #你的邮箱
    :password => "xxxxxx" #你的密码
  }
 
  # Print deprecation notices to the Rails logger
  config.active_support.deprecation = :log
 
  # Only use best-standards-support built into browsers
  config.action_dispatch.best_standards_support = :builtin
end
===============================================
(4)其它配置
随便新建一个home controller
$ rails g controller home index
删除public目录下的index.html文件
修改config/routes.rb文件,添加一句
root :to => "home#index"
编辑app/controllers/home_controller.rb文件
==============================================
class HomeController < ApplicationController
  before_filter :authenticate_user!  #添加这一句
   
  def index
  end
 
end
============================================
编辑app/views/layouts/application.html.erb文件

<!DOCTYPE html>
<html>
<head>
  <title>R2</title>
  <%= stylesheet_link_tag :all %>
  <%= javascript_include_tag :defaults %>
  <%= csrf_meta_tag %>
</head>
<body>
 
#添加以下两句
<p class="notice"><%= notice %></p>
<p class="alert"><%= alert %></p>
 
<%= yield %>
 
</body>
</html>
==============================================
3、运行程序
启动工程:
$ rails s
浏览器输入:http://localhost:3000
结果转到了http://localhost:3000/users/sign_in,要求你登录
我没有账户登录怎么办?点击sign_up注册账户
填写email、密码,点击“sign up ”,不出意外的话去注册邮箱收取确认邮件吧!
==============================================
Devise:        #执行命令
  devise
  devise:erb
  devise:form_for
  devise:install
  devise:markerb
  devise:shared_views
  devise:simple_form_for
  devise:views

在controller添加=> before_filter :authenticate_user!  <=就可以加登录

        获取当前用户current_user

 

        new_user_session GET    /users/sign_in(.:format)          devise/sessions#new
            user_session POST   /users/sign_in(.:format)          devise/sessions#create
    destroy_user_session DELETE /users/sign_out(.:format)         devise/sessions#destroy
           user_password POST   /users/password(.:format)         devise/passwords#create
       new_user_password GET    /users/password/new(.:format)     devise/passwords#new
      edit_user_password GET    /users/password/edit(.:format)    devise/passwords#edit
                         PUT    /users/password(.:format)         devise/passwords#update
cancel_user_registration GET    /users/cancel(.:format)           devise/registrations#cancel
       user_registration POST   /users(.:format)                  devise/registrations#create
   new_user_registration GET    /users/sign_up(.:format)          devise/registrations#new
  edit_user_registration GET    /users/edit(.:format)             devise/registrations#edit
                         PUT    /users(.:format)                  devise/registrations#update
                         DELETE /users(.:format)                  devise/registrations#destroy
       user_confirmation POST   /users/confirmation(.:format)     devise/confirmations#create
   new_user_confirmation GET    /users/confirmation/new(.:format) devise/confirmations#new
                         GET    /users/confirmation(.:format)     devise/confirmations#show
             user_unlock POST   /users/unlock(.:format)           devise/unlocks#create
         new_user_unlock GET    /users/unlock/new(.:format)       devise/unlocks#new
                         GET    /users/unlock(.:format)           devise/unlocks#show

一个注册、登录程序就完成了!
分享到:
评论

相关推荐

    rails3-mongoid-devise, 示例 Rails 3.2应用,带有数据 Mongoid,用于验证.zip

    rails3-mongoid-devise, 示例 Rails 3.2应用,带有数据 Mongoid,用于验证 Rails 4.1有关设计的Rails 4.1示例应用程序,请参见:rails设计有一个用于设计的教程:Rails 设计教程。类似示例和教程这是来自 RailsApps...

    Rails上的API:使用Rails构建REST APIAPIs on Rails: Building REST APIs with Rails

    4. **添加认证逻辑**:为了保护敏感数据,可以使用Devise或其他认证插件实现用户登录验证。 5. **测试API**:使用Postman等工具发送请求,测试API是否按预期工作。 通过以上步骤,我们可以构建出一个基本可用的...

    使用Rails、Vue、GraphQL和Devise进行令牌身份验证_Rub.zip

    在本文中,我们将深入探讨如何使用Rails、Vue.js、GraphQL和Devise来构建一个具有令牌身份验证的Web应用。Rails是Ruby on Rails框架,用于后端开发,Vue.js是一种轻量级的前端JavaScript框架,而GraphQL是一种强大的...

    源代码 for web开发敏捷之道:应用rails进行敏捷web开发(原书第4版)

    10. **Rails插件和gem**:介绍如何利用社区的插件和gem扩展Rails的功能,例如Devise用于用户认证,CanCanCan处理授权,或者Paperclip或Carrierwave处理文件上传。 11. **AJAX和JavaScript**:了解如何在Rails中集成...

    rails_grape_auth:用于devise_token_auth + grape_devise_token_auth的测试Rails应用

    标题中的“rails_grape_auth”是一个专门为Rails应用设计的组件,用于实现身份验证功能,它与“devise_token_auth”和“grape_devise_token_auth”这两个库相结合,提供了RESTful API的身份验证解决方案。...

    api_guard:用于Rails API的JWT身份验证解决方案

    API防护 基于的身份验证解决方案,针对基于Rails的API进行令牌刷新... 请参阅以配置API Guard身份验证以与Devise一起使用,而不是使用has_secure_password 。 class User &lt; ApplicationRecord has_secure_passworde

    使用Rails4Devise和Grape验证API_JavaScript_CSS_下载.zip

    标题中的“使用Rails4Devise和Grape验证API”揭示了这个项目是关于在Ruby on Rails 4框架中实现用户认证的。Devise是一个灵活的身份验证解决方案,它为Rails应用提供了许多常见的身份验证需求,如注册、登录、密码...

    ember-cli-simple-auth-devise:从 Ember CLI 向 RailsDevise 服务器进行身份验证

    从 Ember CLI 应用程序对 Rails/Devise 服务器进行身份验证。 用于构建此项目的分步指南: 当前版本 该项目目前正在使用: 余烬cli 0.1.1 余烬简单身份验证 0.6.7 导轨 4.1.8 建造 git clone ...

    StimulusReflex、CableReady、Turbo、Vite、Devise、Rails7准.zip

    3. **Turbo**(原名TurboLinks):这是Rails框架内置的一个特性,用于加速页面加载。它通过只更新页面的部分内容而不是整个页面,减少了HTTP请求的数量,提升了页面导航的速度和用户体验。 4. **Vite**:Vite是由...

    使用Rails5构建的社交网络。使用devise进行身份验.zip

    在本项目中,我们探讨了如何使用Ruby on Rails 5框架构建一个社交网络平台,并集成Devise进行身份验证。Rails是基于MVC(模型-视图-控制器)架构模式的开源Web应用程序框架,它使开发者能够高效地创建数据驱动的网站...

    关于Rails登录和验证插件http_authentication restful-authentication

    然而,随着Rails的发展,这个插件逐渐被devise等现代认证解决方案所取代,devise提供了更多的特性和灵活性,比如多因素认证、邮箱验证、确认和锁定策略等。 在实际项目中,理解并正确使用http_authentication和...

    authy-devise:Authy Devise插件添加了双重身份验证

    权威设计 这是一个扩展,用于将添加到Rails应用程序。OneTouch支持通用身份验证令牌支持Rails 5 CSRF保护运行测试注意:Twilio Authy API的沙盒功能将于2021年9月30日停止运行版权 先决条件要使用Authy API,您需要...

    Advanced Rails

    7. **Rails插件与Gem**:Rails社区提供了丰富的插件和Gem,如Devise用于身份验证,Paperclip或Carrierwave处理文件上传,Resque或Sidekiq实现后台任务队列。掌握如何选择和使用这些工具来扩展应用功能。 8. **Rails...

    rodauth-rails:用于Rodauth身份验证框架的Rails集成

    已经有几种流行的Rails身份验证解决方案(Devise,Sorcery,Clearance,Authlogic),那么为什么要选择Rodauth? 以下是一些让我脱颖而出的优势: 多因素身份验证( , ,, ) 标准化的(适用于所有功能) 企业...

    ruby on rails 2.3.5 api html版

    10. **插件和Gem**:Rails的生态系统中,Gem是第三方库的主要形式,它们提供了额外的功能,如Devise用于身份验证,CanCanCan用于授权,Paperclip或Carrierwave处理文件上传等。 11. **部署**:了解如何将Rails应用...

    Railsgem用于添加Facebook身份验证功能以使用koala进.zip

    在Ruby on Rails开发中,集成社交媒体身份验证是一个常见的需求,以提供用户更加便捷的登录方式。本教程将详细讲解如何使用Rails gem(装置Devise)和Koala库来实现Facebook的身份验证功能。 首先,我们需要了解`...

    stee.vn:个人 Rails 网站

    7. **Rails 插件和 gems**:Rails 社区提供了大量的 gems(类似于其他语言的库或模块),用于扩展功能,如 Devise 用于身份验证,carrierwave 或 paperclip 处理文件上传等。 8. **响应式设计**:考虑到网站的跨...

    使用devise+omniauth进行谷歌身份验证_Ruby_JavaScript_.zip

    在Ruby on Rails应用中,Devise和OmniAuth是两种常用的工具,用于实现用户认证和第三方身份验证。在这个教程中,我们将深入探讨如何利用这两者来实现谷歌身份验证。这将帮助你的用户通过他们的谷歌账户登录,提升...

    ruby-bank:在 Rails 上学习 ruby

    理解如何管理和使用Gems,如Devise用于身份验证,CanCanCan进行授权等,将帮助你构建功能丰富的应用。 10. **版本控制**:项目可能使用Git进行版本控制,你需要掌握如何使用Git进行代码提交、分支管理和合并,以便...

Global site tag (gtag.js) - Google Analytics