bpluser 0.0.26 → 0.1.12

data/app/models/bpluser/user.rb

@@ -1,213 +0,0 @@
-module Bpluser::User
-
-
-  def self.included(base)
-    #, :validatable
-    base.send :devise, :database_authenticatable, :registerable,
-              :recoverable, :rememberable, :trackable, :omniauthable, :omniauth_providers => [:ldap, :polaris, :facebook]
-    #base.send :attr_accessible, :provider, :username, :email, :password, :password_confirmation, :remember_me, :first_name, :last_name, :display_name, :uid
-    base.send :has_many, :user_institutions, :class_name => "Bpluser::UserInstitution"
-    base.send :has_many, :folders, :dependent => :destroy, :class_name => "Bpluser::Folder"
-    base.extend(ClassMethods)
-    base.send :include, InstanceMethods
-
-    #Include custom validation that doesn't require email to be uniqe. Based on: https://github.com/plataformatec/devise/blob/master/lib/devise/models/validatable.rb
-    base.send :include, Bpluser::Validatable
-
-  end
-
-  module ClassMethods
-    def find_for_ldap_oauth(auth_response, signed_in_resource=nil)
-
-
-      ldap_raw_details = auth_response[:extra][:raw_info]
-      ldap_info_details = auth_response[:info]
-
-      user = User.where(:provider => auth_response.provider, :uid => ldap_raw_details.samaccountname[0].downcase).first
-
-      #first_name:ldap_info_details.first_name,
-      #last_name:ldap_info_details.last_name,
-      unless user
-        user = User.create(provider:auth_response.provider,
-                           uid:ldap_raw_details.samaccountname[0].downcase,
-                           username:ldap_raw_details.samaccountname[0].downcase,
-                           email:ldap_raw_details.mail[0].to_s.downcase,
-                           password:Devise.friendly_token[0,20],
-                           display_name: ldap_info_details.first_name + " " + ldap_info_details.last_name,
-                           first_name: ldap_info_details.first_name,
-                           last_name: ldap_info_details.last_name
-        )
-      end
-      groups = user.ldap_groups
-      groups.each do |group|
-        if(group == "Repository Administrators")
-          superuser_role = Role.where(:name=>'superuser').first
-          if(superuser_role == nil)
-            superuser_role = Role.create(:name=>"superuser")
-          end
-          user.roles << superuser_role unless user.roles.include?(superuser_role)
-          user.save!
-
-          admin_role = Role.where(:name=>'admin').first
-          if(admin_role == nil)
-            admin_role = Role.create(:name=>"admin")
-          end
-          user.roles << admin_role unless user.roles.include?(admin_role)
-          user.save!
-        end
-
-      end
-
-      user
-    end
-
-    def find_for_polaris_oauth(auth_response, signed_in_resource=nil)
-      polaris_raw_details = auth_response[:extra][:raw_info]
-      polaris_info_details = auth_response[:info]
-
-      user = User.where(:provider => auth_response.provider, :uid => auth_response[:uid]).first
-
-      #first_name:ldap_info_details.first_name,
-      #last_name:ldap_info_details.last_name,
-      unless user
-        email_value = polaris_info_details[:email].present? ? polaris_info_details[:email] : ''
-        #For some reason, User.create has no id set despite that intending to be autocreated. Unsure what is up with that. So trying this.
-        user = User.new(provider:auth_response.provider,
-                           uid:auth_response[:uid],
-                           username:polaris_info_details[:first_name],
-                           email:email_value,
-                           password:Devise.friendly_token[0,20],
-                           display_name:polaris_info_details[:first_name] + " " + polaris_info_details[:last_name],
-                           first_name: polaris_info_details[:first_name],
-                           last_name: polaris_info_details[:last_name]
-
-        )
-        user.save!
-
-      end
-      user
-    end
-
-    def find_for_facebook_oauth(auth, signed_in_resource=nil)
-      user = User.where(:provider => auth.provider, :uid => auth.uid).first
-      unless user
-        user = User.create(display_name:auth.extra.raw_info.name,
-                           uid:auth.uid,
-                           provider:auth.provider,
-                           username:auth.info.nickname,
-                           email:auth.info.email,
-                           password:Devise.friendly_token[0,20] ,
-                           first_name:auth.extra.raw_info.first_name,
-                           last_name:auth.extra.raw_info.last_name
-        )
-      end
-      user
-    end
-
-    def find_for_local_auth(auth, signed_in_resource=nil)
-      user = User.where(:provider => auth.provider, :uid => auth.uid).first
-      unless user
-        user = User.create(display_name:auth.full_name,
-                           uid:auth.uid,
-                           provider:auth.provider,
-                           username:auth.uid,
-                           email:auth.email,
-                           password:auth.password,
-                           first_name:auth.first_name,
-                           last_name:auth.last_name
-        )
-      end
-      user
-    end
-
-
-
-
-    # This method should find User objects using the user_key you've chosen.
-    # By default, uses the unique identifier specified in by devise authentication_keys (ie. find_by_id, or find_by_email).
-    # You must have that find method implemented on your user class, or must override find_by_user_key
-    #def find_by_user_key(key)
-      #self.send("find_by_#{Devise.authentication_keys.first}".to_sym, key)
-    #end
-  end
-
-  #has_and_belongs_to_many :groups
-
-  # Method added by Blacklight; Blacklight uses #to_s on your
-  # user class to get a user-displayable login/identifier for
-  # the account.
-
-  # The following methods will be included in any active model object
-  # that calls "is_blacklight_user"
-  module InstanceMethods
-
-
-    def to_s
-      self.username
-    end
-
-    def name
-      return self.username rescue self.display_name.titleize
-    end
-
-    def user_key
-      send(Devise.authentication_keys.first)
-    end
-
-
-    def ldap_groups
-      #Hydra::LDAP.groups_for_user(username + ",dc=psu,dc=edu")
-      #['archivist', 'admin_policy_object_editor']
-
-      Hydra::LDAP.groups_for_user(Net::LDAP::Filter.eq('samaccountname', self.username), ['memberOf'])  { |result| result.first[:memberOf].select{ |y| y.starts_with? 'CN=' }.map{ |x| x.sub(/^CN=/, '').sub(/,OU=Private Groups,DC=private,DC=bpl,DC=org/, '').sub(/,OU=Distribution Lists/, '').sub(/,OU=Security Groups/, '') } } rescue []
-    end
-
-    def populate_attributes
-
-    end
-
-    def default_user_groups
-      # # everyone is automatically a member of the group 'public'
-      #['public', 'test']
-    end
-
-    def get_uploads_collection
-      query="rightsMetadata_edit_access_machine_person_t:#{uid} AND title_s:Uploads AND has_model_s:info\\:fedora/afmodel\\:DILCollection"
-      ActiveFedora::SolrService.query(query, {:fl=>'id title_t'})
-    end
-
-    def get_details_collection
-      query="rightsMetadata_edit_access_machine_person_t:#{uid} AND title_s:Details AND has_model_s:info\\:fedora/afmodel\\:DILCollection"
-      ActiveFedora::SolrService.query(query, {:fl=>'id title_t'})
-    end
-
-    def collections
-      query="rightsMetadata_edit_access_machine_person_t:#{uid} AND NOT title_t:Uploads AND NOT title_t:Details AND has_model_s:info\\:fedora/afmodel\\:DILCollection"
-      ActiveFedora::SolrService.query(query, {:fl=>'id title_t'})
-    end
-
-    def existing_folder_item_for (document_id)
-      self.folders.find do |fldr|
-        fldr.folder_items.find do |fldr_itm|
-          return fldr_itm if fldr_itm.document_id == document_id
-        end
-      end
-    end
-
-    def superuser?
-      roles.where(name: 'superuser').exists?
-    end
-
-    def permanent_account?
-      return self.provider != 'digital_stacks_temporary'
-    end
-
-    def email_not_required?
-      if self.provider != 'digital_stacks_temporary' and self.provider != 'polaris'
-        return true
-      end
-      return false
-    end
-
-  end
-end

data/app/models/bpluser/validatable.rb

@@ -1,63 +0,0 @@
-#By default, devise requires an email to be unique. I want the email checks but need to remove the uniqueness...
-module Bpluser::Validatable
-  # Validatable creates all needed validations for a user email and password.
-  # It's optional, given you may want to create the validations by yourself.
-  # Automatically validate if the email is present, unique and its format is
-  # valid. Also tests presence of password, confirmation and length.
-  #
-  # == Options
-  #
-  # Validatable adds the following options to devise_for:
-  #
-  #   * +email_regexp+: the regular expression used to validate e-mails;
-  #   * +password_length+: a range expressing password length. Defaults to 8..72.
-  #
-    # All validations used by this module.
-    VALIDATIONS = [:validates_presence_of, :validates_format_of,
-                   :validates_confirmation_of, :validates_length_of].freeze
-
-    def self.required_fields(klass)
-      []
-    end
-
-    def self.included(base)
-      base.extend ClassMethods
-      assert_validations_api!(base)
-
-      base.class_eval do
-        validates_presence_of   :email, if: [:email_required?, :email_not_required?]
-        #validates_uniqueness_of :email, allow_blank: true, if: :email_changed?
-        validates_format_of     :email, with: email_regexp, allow_blank: true, if: [:email_changed?, :email_not_required?]
-
-        validates_presence_of     :password, if: :password_required?
-        validates_confirmation_of :password, if: :password_required?
-        validates_length_of       :password, within: password_length, allow_blank: true
-      end
-    end
-
-    def self.assert_validations_api!(base) #:nodoc:
-      unavailable_validations = VALIDATIONS.select { |v| !base.respond_to?(v) }
-
-      unless unavailable_validations.empty?
-        raise "Could not use :validatable module since #{base} does not respond " <<
-                  "to the following methods: #{unavailable_validations.to_sentence}."
-      end
-    end
-
-    protected
-
-    # Checks whether a password is needed or not. For validations only.
-    # Passwords are always required if it's a new record, or if the password
-    # or confirmation are being set somewhere.
-    def password_required?
-      !persisted? || !password.nil? || !password_confirmation.nil?
-    end
-
-    def email_required?
-      true
-    end
-
-    module ClassMethods
-      ::Devise::Models.config(self, :email_regexp, :password_length)
-    end
-  end

data/app/views/layouts/bpluser/application.html.erb

@@ -1,14 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-  <title>Bpluser</title>
-  <%= stylesheet_link_tag    "bpluser/application", :media => "all" %>
-  <%= javascript_include_tag "bpluser/application" %>
-  <%= csrf_meta_tags %>
-</head>
-<body>
-
-<%= yield %>
-
-</body>
-</html>

data/test/bpluser_test.rb

@@ -1,7 +0,0 @@
-require 'test_helper'
-
-class BpluserTest < ActiveSupport::TestCase
-  test "truth" do
-    assert_kind_of Module, Bpluser
-  end
-end

data/test/dummy/README.rdoc

@@ -1,261 +0,0 @@
-== Welcome to Rails
-
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
-
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
-
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-
-
-== Getting Started
-
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
-
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
-
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
-
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
-
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
-
-
-== Debugging Rails
-
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.all
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better, you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you can enter "cont".
-
-
-== Console
-
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-
-To start the console, run <tt>rails console</tt> from the application
-directory.
-
-Options:
-
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-
-More information about irb can be found at:
-link:http://www.rubycentral.org/pickaxe/irb.html
-
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-
-== Description of Contents
-
-The default directory structure of a generated Ruby on Rails application:
-
-  |-- app
-  |   |-- assets
-  |       |-- images
-  |       |-- javascripts
-  |       `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- stylesheets
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-
-public
-  The directory available for the web server. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.

data/test/dummy/app/assets/javascripts/application.js

@@ -1,15 +0,0 @@
-// This is a manifest file that'll be compiled into application.js, which will include all the files
-// listed below.
-//
-// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
-// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
-//
-// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
-// the compiled file.
-//
-// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
-// GO AFTER THE REQUIRES BELOW.
-//
-//= require jquery
-//= require jquery_ujs
-//= require_tree .

data/test/dummy/app/assets/stylesheets/application.css

@@ -1,13 +0,0 @@
-/*
- * This is a manifest file that'll be compiled into application.css, which will include all the files
- * listed below.
- *
- * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
- * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
- *
- * You're free to add application-wide styles to this file and they'll appear at the top of the
- * compiled file, but it's generally better to create a new file per style scope.
- *
- *= require_self
- *= require_tree .
- */

data/test/dummy/app/views/layouts/application.html.erb

@@ -1,14 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-  <title>Dummy</title>
-  <%= stylesheet_link_tag    "application", :media => "all" %>
-  <%= javascript_include_tag "application" %>
-  <%= csrf_meta_tags %>
-</head>
-<body>
-
-<%= yield %>
-
-</body>
-</html>

data/test/dummy/config/application.rb

@@ -1,59 +0,0 @@
-require File.expand_path('../boot', __FILE__)
-
-require 'rails/all'
-
-Bundler.require
-require "bpluser"
-
-module Dummy
-  class Application < Rails::Application
-    # Settings in config/environments/* take precedence over those specified here.
-    # Application configuration should go into files in config/initializers
-    # -- all .rb files in that directory are automatically loaded.
-
-    # Custom directories with classes and modules you want to be autoloadable.
-    # config.autoload_paths += %W(#{config.root}/extras)
-
-    # Only load the plugins named here, in the order given (default is alphabetical).
-    # :all can be used as a placeholder for all plugins not explicitly named.
-    # config.plugins = [ :exception_notification, :ssl_requirement, :all ]
-
-    # Activate observers that should always be running.
-    # config.active_record.observers = :cacher, :garbage_collector, :forum_observer
-
-    # Set Time.zone default to the specified zone and make Active Record auto-convert to this zone.
-    # Run "rake -D time" for a list of tasks for finding time zone names. Default is UTC.
-    # config.time_zone = 'Central Time (US & Canada)'
-
-    # The default locale is :en and all translations from config/locales/*.rb,yml are auto loaded.
-    # config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s]
-    # config.i18n.default_locale = :de
-
-    # Configure the default encoding used in templates for Ruby 1.9.
-    config.encoding = "utf-8"
-
-    # Configure sensitive parameters which will be filtered from the log file.
-    config.filter_parameters += [:password]
-
-    # Enable escaping HTML in JSON.
-    config.active_support.escape_html_entities_in_json = true
-
-    # Use SQL instead of Active Record's schema dumper when creating the database.
-    # This is necessary if your schema can't be completely dumped by the schema dumper,
-    # like if you have constraints or database-specific column types
-    # config.active_record.schema_format = :sql
-
-    # Enforce whitelist mode for mass assignment.
-    # This will create an empty whitelist of attributes available for mass-assignment for all models
-    # in your app. As such, your models will need to explicitly whitelist or blacklist accessible
-    # parameters by using an attr_accessible or attr_protected declaration.
-    config.active_record.whitelist_attributes = true
-
-    # Enable the asset pipeline
-    config.assets.enabled = true
-
-    # Version of your assets, change this if you want to expire all your assets
-    config.assets.version = '1.0'
-  end
-end
-

data/test/dummy/config/boot.rb

@@ -1,10 +0,0 @@
-require 'rubygems'
-gemfile = File.expand_path('../../../../Gemfile', __FILE__)
-
-if File.exist?(gemfile)
-  ENV['BUNDLE_GEMFILE'] = gemfile
-  require 'bundler'
-  Bundler.setup
-end
-
-$:.unshift File.expand_path('../../../../lib', __FILE__)

data/test/dummy/config/environment.rb

@@ -1,5 +0,0 @@
-# Load the rails application
-require File.expand_path('../application', __FILE__)
-
-# Initialize the rails application
-Dummy::Application.initialize!