Mozilla has announced that Persona will be shutting down November 2016. warden-browserid relies on the Persona service and will stop functioning properly once Persona is shut down. While it is possible to self-host Persona and configure warden-browserid to rely on your own instance, this is difficult and not recommended. See the wiki page linked above for recommended alternatives to Persona for authentication.

Authenticate your Warden-enabled app using BrowserID from Mozilla

Add this line to your application's Gemfile:

gem 'warden-browserid'

And then execute:

$ bundle

Or install it yourself as:

$ gem install warden-browserid

I use the warden-browserid strategy with Devise, configured like this in config/initializers/devise.rb in Rails:

  config.warden do |manager|
    manager.default_strategies(:scope => :user).unshift :browserid
  end

See the [Warden wiki] 1 for other usage. The following option is available, since [Mozilla] 2 says to use BrowserID as follows:

 manager.browserid_url = "dev.diresworb.org"  # Development (default)
 # manager.browserid_url = "diresworb.org"      # Beta
 # manager.browserid_url = "browserid.org"      # Production
 

I use the [devise-browserid] 3 gem to enable client side action for BrowserID.

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request