pastore 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 44d3e6e0a841c09767bef483f9c53a6c1e11f8a1603671865635a50eb139d0cd
+  data.tar.gz: 246bba109256e0bb1e67c0c5cc518640e99ddd2a0ca01a403a4008fd04c53298
+SHA512:
+  metadata.gz: bc3fb06cbbc9ae2321a486dea657f2e6645ca3e3ceea3e72d36e5cb6733ef16741097fb29e669d4fbc0e64ef072b5f6ac3edc530a3b5abf0048ad93934d5c926
+  data.tar.gz: 8f4d326809b4ed7495a964da19de29a75818a70882c447cef7f202526c764b720bb396f931d879b505fcf49bd7cf85b4d17eee8f3970a915b60d92098c60d8fb

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,10 @@
+AllCops:
+  NewCops: enable
+  TargetRubyVersion: 2.6
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Layout/LineLength:
+  Max: 120

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2023-01-26
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at groza@opinioni.net. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in pastore.gemspec
+gemspec
+
+gem 'faker'
+gem 'rake'
+gem 'rspec-rails'
+gem 'shoulda-matchers'
+gem 'pry'

data/Gemfile.lock

@@ -0,0 +1,188 @@
+PATH
+  remote: .
+  specs:
+    pastore (0.0.1)
+      rails (>= 4.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    actioncable (7.0.4)
+      actionpack (= 7.0.4)
+      activesupport (= 7.0.4)
+      nio4r (~> 2.0)
+      websocket-driver (>= 0.6.1)
+    actionmailbox (7.0.4)
+      actionpack (= 7.0.4)
+      activejob (= 7.0.4)
+      activerecord (= 7.0.4)
+      activestorage (= 7.0.4)
+      activesupport (= 7.0.4)
+      mail (>= 2.7.1)
+      net-imap
+      net-pop
+      net-smtp
+    actionmailer (7.0.4)
+      actionpack (= 7.0.4)
+      actionview (= 7.0.4)
+      activejob (= 7.0.4)
+      activesupport (= 7.0.4)
+      mail (~> 2.5, >= 2.5.4)
+      net-imap
+      net-pop
+      net-smtp
+      rails-dom-testing (~> 2.0)
+    actionpack (7.0.4)
+      actionview (= 7.0.4)
+      activesupport (= 7.0.4)
+      rack (~> 2.0, >= 2.2.0)
+      rack-test (>= 0.6.3)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.0, >= 1.2.0)
+    actiontext (7.0.4)
+      actionpack (= 7.0.4)
+      activerecord (= 7.0.4)
+      activestorage (= 7.0.4)
+      activesupport (= 7.0.4)
+      globalid (>= 0.6.0)
+      nokogiri (>= 1.8.5)
+    actionview (7.0.4)
+      activesupport (= 7.0.4)
+      builder (~> 3.1)
+      erubi (~> 1.4)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.1, >= 1.2.0)
+    activejob (7.0.4)
+      activesupport (= 7.0.4)
+      globalid (>= 0.3.6)
+    activemodel (7.0.4)
+      activesupport (= 7.0.4)
+    activerecord (7.0.4)
+      activemodel (= 7.0.4)
+      activesupport (= 7.0.4)
+    activestorage (7.0.4)
+      actionpack (= 7.0.4)
+      activejob (= 7.0.4)
+      activerecord (= 7.0.4)
+      activesupport (= 7.0.4)
+      marcel (~> 1.0)
+      mini_mime (>= 1.1.0)
+    activesupport (7.0.4)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 1.6, < 2)
+      minitest (>= 5.1)
+      tzinfo (~> 2.0)
+    builder (3.2.4)
+    coderay (1.1.3)
+    concurrent-ruby (1.1.10)
+    crass (1.0.6)
+    date (3.3.2)
+    diff-lcs (1.5.0)
+    erubi (1.11.0)
+    faker (3.1.0)
+      i18n (>= 1.8.11, < 2)
+    globalid (1.0.0)
+      activesupport (>= 5.0)
+    i18n (1.12.0)
+      concurrent-ruby (~> 1.0)
+    loofah (2.19.1)
+      crass (~> 1.0.2)
+      nokogiri (>= 1.5.9)
+    mail (2.8.0)
+      mini_mime (>= 0.1.1)
+      net-imap
+      net-pop
+      net-smtp
+    marcel (1.0.2)
+    method_source (1.0.0)
+    mini_mime (1.1.2)
+    mini_portile2 (2.8.0)
+    minitest (5.17.0)
+    net-imap (0.3.2)
+      date
+      net-protocol
+    net-pop (0.1.2)
+      net-protocol
+    net-protocol (0.2.1)
+      timeout
+    net-smtp (0.3.3)
+      net-protocol
+    nio4r (2.5.8)
+    nokogiri (1.13.10)
+      mini_portile2 (~> 2.8.0)
+      racc (~> 1.4)
+    pry (0.14.2)
+      coderay (~> 1.1)
+      method_source (~> 1.0)
+    racc (1.6.1)
+    rack (2.2.4)
+    rack-test (2.0.2)
+      rack (>= 1.3)
+    rails (7.0.4)
+      actioncable (= 7.0.4)
+      actionmailbox (= 7.0.4)
+      actionmailer (= 7.0.4)
+      actionpack (= 7.0.4)
+      actiontext (= 7.0.4)
+      actionview (= 7.0.4)
+      activejob (= 7.0.4)
+      activemodel (= 7.0.4)
+      activerecord (= 7.0.4)
+      activestorage (= 7.0.4)
+      activesupport (= 7.0.4)
+      bundler (>= 1.15.0)
+      railties (= 7.0.4)
+    rails-dom-testing (2.0.3)
+      activesupport (>= 4.2.0)
+      nokogiri (>= 1.6)
+    rails-html-sanitizer (1.4.4)
+      loofah (~> 2.19, >= 2.19.1)
+    railties (7.0.4)
+      actionpack (= 7.0.4)
+      activesupport (= 7.0.4)
+      method_source
+      rake (>= 12.2)
+      thor (~> 1.0)
+      zeitwerk (~> 2.5)
+    rake (13.0.6)
+    rspec-core (3.12.0)
+      rspec-support (~> 3.12.0)
+    rspec-expectations (3.12.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-mocks (3.12.3)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-rails (6.0.1)
+      actionpack (>= 6.1)
+      activesupport (>= 6.1)
+      railties (>= 6.1)
+      rspec-core (~> 3.11)
+      rspec-expectations (~> 3.11)
+      rspec-mocks (~> 3.11)
+      rspec-support (~> 3.11)
+    rspec-support (3.12.0)
+    shoulda-matchers (5.3.0)
+      activesupport (>= 5.2.0)
+    thor (1.2.1)
+    timeout (0.3.1)
+    tzinfo (2.0.5)
+      concurrent-ruby (~> 1.0)
+    websocket-driver (0.7.5)
+      websocket-extensions (>= 0.1.0)
+    websocket-extensions (0.1.5)
+    zeitwerk (2.6.6)
+
+PLATFORMS
+  x86_64-linux
+
+DEPENDENCIES
+  faker
+  pastore!
+  pry
+  rake
+  rspec-rails
+  shoulda-matchers
+
+BUNDLED WITH
+   2.3.24

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 Demetra Opinioni.net Srl
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,238 @@
+# Pastore
+
+Pastore is a powerful gem for Rails that simplifies the process of validating parameters and controlling access to actions in your controllers.
+With Pastore, you can easily define validations for your parameters, ensuring that they meet specific requirements before being passed to your controller actions.
+Additionally, Pastore allows you to easily control access to your actions, ensuring that only authorized users can access sensitive information.
+With its intuitive interface and robust features, Pastore is a must-have tool for any Rails developer looking to improve the security and reliability of their application.
+
+## Installation
+
+Install the gem and add to the application's Gemfile by executing:
+
+    bundle add pastore
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+    gem install pastore
+
+## Usage
+
+Pastore gem implements 2 main features: `Guards` and `Validators`. Guards are intended to be used for action access control, while Validators are intended to be used for actions params validation.
+
+### Guards usage
+
+`Guards` feature allows you to define access control logic for actions in Rails controllers. To use the `Guards` you have to include `Pastore::Guards` into your Rails controller.
+
+##### Setup
+
+The best way to start using the `Guards` feature is to add the following code to your `ApplicationController`:
+
+```ruby
+# app/controllers/application_controller.rb
+
+class ApplicationController < ActionController::API
+  include Pastore::Guards
+
+  # Specify the logic for current user's role detection, which will be used to check
+  # if current user is authorized to access a specific action.
+  detect_role do
+    current_user&.role
+  end
+end
+```
+
+In this way all your controllers will inherit the authorization settings from `ApplicationController`. Then in your controller you can do something like this:
+
+```ruby
+class MyController < ApplicationController
+  # By default a :deny strategy is used, so with #permit_role we're going
+  # to specify which roles are allowed to access this action.
+  permit_role :admin, :user, :pm
+  def index
+    # ... action code ...
+  end
+
+  # Without a `permit_role` definition the access to this action will be denied to everyone.
+  def not_allowed_action
+    # ... action code ...
+  end
+end
+```
+
+If you want to use `Guards` only in specific controllers, just include `Pastore::Guards` and define `detect_role` in your controller:
+
+```ruby
+class CustomController < ApplicationController
+  include Pastore::Guards
+
+  detect_role do
+    current_user&.role
+  end
+
+  permit_role :admin, :supervisor
+  def index
+    # ... action code ...
+  end
+end
+```
+
+#### Custom authorization logic
+
+If checking user's role is not enough, you can use the `authorize_with` helper, which will allow you to specify a custom access logic by providing a method name (where custom logic is defined) or a block to use for access verification. As a result your block or method should return `true` if access is granted, or `false` otherwise.
+
+```ruby
+class MyController < ApplicationController
+  # You can override the role detection logic inside a controller if it's necessary by
+  # using the `detect_role` helper.
+  detect_role do
+    current_user&.selected_role
+  end
+
+  # If you want to use a custom/dynamic authorization logic, you can
+  # specify your own implementation in a method.
+  authorize_with :custom_authorization
+  def index
+    # ... action code ...
+  end
+
+  # You can also specify the authorization logic in a block.
+  authorize_with { custom_authorized? }
+  def show
+    # ... action code ...
+  end
+
+  # Allow only users with `admin` role to access this action.
+  permit_role :admin
+  def update
+  end
+
+  private
+
+  # Specify a custom authorization logic (return `true` if successful and `false` when forbidden).
+  def custom_authorization
+    # ... your custom authorization logic here ...
+  end
+end
+```
+
+#### Using `allow` strategy
+
+**!!! WARNING !!!** Be careful when using `allow` strategy, because when enabled it grants access to every action in the controller, which could potentially lead to security issues.
+
+By default `Pastore::Guards` will use `deny` strategy, which means that the access is denied by default, and the only way to access it is through explicit authorization.
+
+Sometimes you might prefer a `allow` strategy instead, in order to allow access to any action within the controller, and manually restrict access to specified actions and roles.
+
+For doing so you can use `use_allow_strategy!`, which changes the default strategy. In this case you should use `deny_role` to disable the access for a specific role or overwrite authorization strategy for specific actions with `authorize_with` helper.
+
+
+
+```ruby
+class MyController < ApplicationController
+  # By default allow access to any action within the controller by any role.
+  use_allow_strategy!
+
+  # In this case we're using the :allow strategy, so if we want to exclude a specific role
+  # we can do it by using #deny_role method.
+  deny_role :user
+  def index
+    # ... action code ...
+  end
+
+  # Check access by using a custom method
+  authorize_with :custom_autorization
+  def restricted_access_action
+    # ... action code ...
+  end
+
+  # Check access by using a block
+  authorize_with { current_user&.role == 'admin' }
+  def restricted_access_action2
+    # ... action code ...
+  end
+
+  private
+
+  # Specify a custom authorization logic (return `true` if successful and `false` when forbidden).
+  def custom_autorization
+    # ... custom authorization logic ...
+  end
+end
+```
+
+#### Using `skip_guards`
+
+Sometime you may want to disable the `Guards` feature for specific actions. For doing so you can use the `skip_guards` helper, which allows you to specify the list of actions for which guards check have to be disabled. In the example below the access to `index` and `show` actions is granted by `skip_guards` which bypasses the guards check. `skip_guards` have priority over `permit_role`, `deny_role` and `authorize_with`, so using those helpers on actions with disabled guards will have no effect and the access will be granted anyway.
+
+```ruby
+class CustomController < ApplicationController
+  use_deny_strategy!
+  skip_guards :index, :show
+
+  def index
+    # ... action code ...
+  end
+
+  authorize_with { false } # this will be ignored because of `skip_guards`
+  def show
+    # ... action code ...
+  end
+end
+```
+
+You can also use `skip_guards` helper with `:except` key, which is useful when you need to disable
+guards for all the actions except a few:
+
+```ruby
+class CustomController < ApplicationController
+  # disable guards for :action_one and :action_two
+  skip_guards except: %i[action_one action_two]
+
+  # Guards DISABLED
+  def index
+    # ... action code ...
+  end
+
+  # Guards ENABLED
+  def action_one
+    # ... action code ...
+  end
+
+  # Guards ENABLED
+  def action_two
+    # ... action code ...
+  end
+
+  # Guards DISABLED
+  def action_three
+    # ... action code ...
+  end
+end
+```
+
+#### `Pastore::Guards` features
+
+Below you can find the list of methods implemented by `Pastore::Guards`, that can be used inside
+your Rails Controller.
+
+| Method | Description |
+|--------|-------------|
+| `use_deny_strategy!` | Set to `deny` the default authorization strategy, which meands that by default the access to the actions will be denied |
+| `use_allow_strategy!` | Set to `allow` the default authorization strategy, which automatically authorizes the access to all the actions. **!!! WARNING !!!** Be careful when using `allow` strategy, because that way any user can access any action of your controller, including guest users if not filtered before. |
+| `detect_role(&block)` | Allows to specify the logic for user role detection. This block will be automatically called to get current user's role information. |
+| `permit_role(*roles)` | Specifies the roles that are allowed to access the action that follows. |
+| `deny_role(*roles)` | Specifies the roles that are not allowed to access the action that follows. |
+| `authorize_with(Symbol|&block)` | Allows to specify a custom authorization logic to use for action access check. Accepts a method name or a block. |
+| `skip_guards(*Symbol|*String, except: *Symbol|*String)` | Allows to disable guards for specific actions. Accepts a list of actions for which to disable guards (e.g. `skip_guards :index, 'show'`), but can be also used to disable guards for all the actions except specified (e.g. `skip_guards except: :index`). |
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at <https://github.com/demetra-it/pastore>. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/demetra-it/pastore/blob/master/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Pastore project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/pastore/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new
+
+task default: %i[spec rubocop]

data/lib/pastore/guards.rb

@@ -0,0 +1,182 @@
+# frozen_string_literal: true
+
+require 'active_support/concern'
+
+module Pastore
+  # Implements the features for Rails controller access guards.
+  module Guards # rubocop:disable Metrics/ModuleLength
+    extend ActiveSupport::Concern
+
+    included do
+      before_action :pastore_check_access
+    end
+
+    class_methods do # rubocop:disable Metrics/BlockLength
+      attr_accessor :_role_detector, :_default_strategy, :_action_permitted_roles, :_controller_allowed_roles,
+                    :_forbidden_callback, :_action_authorization_lambda, :_controller_authorization_lambdas,
+                    :_action_denied_roles, :_controller_denied_roles, :_actions_with_skipped_guards,
+                    :_actions_with_active_guards
+
+      # Sets the logic to use for current role detection.
+      def detect_role(&block)
+        self._role_detector = block
+      end
+
+      # Specifies a custom callback to be called when access is forbidden.
+      def forbidden(&block)
+        self._forbidden_callback = block
+      end
+
+      # Sets the default strategy to "deny".
+      def use_deny_strategy!
+        self._default_strategy = :deny
+      end
+
+      # Sets the default strategy to "allow".
+      def use_allow_strategy!
+        self._default_strategy = :allow
+      end
+
+      # Returns the default strategy.
+      def pastore_default_strategy
+        _default_strategy || :deny
+      end
+
+      def skip_guards(*actions, except: [])
+        self._actions_with_active_guards = [except].flatten.compact.map(&:to_sym)
+        self._actions_with_skipped_guards = actions.flatten.compact.map(&:to_sym)
+      end
+
+      def actions_with_active_guards
+        _actions_with_active_guards || []
+      end
+
+      def actions_with_skipped_guards
+        _actions_with_skipped_guards || []
+      end
+
+      # Specify the list of roles allowed to access the action.
+      def permit_role(*roles)
+        self._action_permitted_roles = [roles].flatten.compact.uniq.map(&:to_s)
+      end
+
+      # Specify the list of roles denied to access the action.
+      def deny_role(*roles)
+        self._action_denied_roles = [roles].flatten.compact.uniq.map(&:to_s)
+      end
+
+      # Specify a custom lambda to be called to authorize the action.
+      def authorize_with(method_name = nil, &block)
+        custom_lambda = method_name.to_sym if method_name.is_a?(Symbol) || method_name.is_a?(String)
+        custom_lambda = block if block_given?
+
+        if custom_lambda.present?
+          self._action_authorization_lambda = custom_lambda
+        else
+          raise ArgumentError, 'A block or a method name must be provided'
+        end
+      end
+
+      # Save the configurations of the action when the action is defined.
+      def method_added(name, *args) # rubocop:disable Metrics/AbcSize, Metrics/MethodLength
+        unless _action_permitted_roles.blank?
+          self._controller_allowed_roles ||= {}
+          self._controller_allowed_roles[name] = _action_permitted_roles
+          self._action_permitted_roles = nil
+        end
+
+        unless _action_denied_roles.blank?
+          self._controller_denied_roles ||= {}
+          self._controller_denied_roles[name] = _action_denied_roles
+          self._action_denied_roles = nil
+        end
+
+        unless _action_authorization_lambda.blank?
+          self._controller_authorization_lambdas ||= {}
+          self._controller_authorization_lambdas[name] = _action_authorization_lambda
+          self._action_authorization_lambda = nil
+        end
+
+        super
+      end
+    end
+
+    protected
+
+    # Returns the current role detected by the role detector logic.
+    def pastore_current_role
+      self.class._role_detector&.call&.to_s
+    end
+
+    # Returns the list of roles allowed to access current action.
+    def pastore_allowed_roles
+      self.class._controller_allowed_roles&.dig(action_name.to_sym) || []
+    end
+
+    # Returns the list of roles denied to access current action.
+    def pastore_denied_roles
+      self.class._controller_denied_roles&.dig(action_name.to_sym) || []
+    end
+
+    # Returns the custom lambda to be called to authorize the action.
+    def pastore_authorization_lambda
+      self.class._controller_authorization_lambdas&.dig(action_name.to_sym)
+    end
+
+    def skip_pastore_guards?
+      active_guards = self.class._actions_with_active_guards
+
+      # If current action is listed in `:except` field of `skip_guards`, then we have to run guards (return false).
+      return false if active_guards&.include?(action_name.to_sym)
+
+      # If `skip_guards` has specified an `:except` field, then we can skip guards, because current action has
+      # implicitely been marked as "to skip guards".
+      return true if active_guards.present?
+
+      # If `skip_guards` don't have the any `except` field, just check if current actions is listed in
+      # `skip_guards`.
+      return true if self.class._actions_with_skipped_guards&.include?(action_name.to_sym)
+
+      # Current action isn't listed in `skip_guards`, so we have to run guards (return false).
+      false
+    end
+
+    # Performs the access check for current action.
+    def pastore_check_access # rubocop:disable Metrics/AbcSize, Metrics/MethodLength, Metrics/CyclomaticComplexity
+      return if skip_pastore_guards?
+
+      if pastore_authorization_lambda.present?
+        authorized = instance_eval(&pastore_authorization_lambda) if pastore_authorization_lambda.is_a?(Proc)
+        authorized = send(pastore_authorization_lambda) if pastore_authorization_lambda.is_a?(Symbol)
+
+        return if authorized
+
+        return pastore_deny_access!
+      end
+
+      case self.class.pastore_default_strategy
+      when :deny then check_access_with_deny_strategy
+      when :allow then check_access_with_allow_strategy
+      end
+    end
+
+    def check_access_with_deny_strategy
+      return pastore_deny_access! unless pastore_allowed_roles.include?(pastore_current_role)
+    end
+
+    def check_access_with_allow_strategy
+      return pastore_deny_access! if pastore_denied_roles.include?(pastore_current_role)
+    end
+
+    def pastore_deny_access!
+      callback = self.class._forbidden_callback
+
+      if callback
+        instance_eval(&callback)
+        response.status = :forbidden
+      else
+        render json: { message: 'Forbidden' }, status: :forbidden
+      end
+    end
+  end
+end

data/lib/pastore/params_validators.rb

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+
+module Pastore
+  # Implements the features for Rails controller params validation.
+  module ParamsValidators
+  end
+end

data/lib/pastore/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Pastore
+  VERSION = '0.0.1'
+end

data/lib/pastore.rb

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require_relative 'pastore/version'
+require_relative 'pastore/guards'
+require_relative 'pastore/params_validators'
+
+module Pastore
+  class Error < StandardError; end
+  # Your code goes here...
+end

metadata

@@ -0,0 +1,84 @@
+--- !ruby/object:Gem::Specification
+name: pastore
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+platform: ruby
+authors:
+- Groza Sergiu
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2023-01-31 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rails
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '4.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '4.0'
+description: |
+  Pastore is a powerful gem for Rails that simplifies the process of
+  validating parameters and controlling access to actions in your controllers.
+  With Pastore, you can easily define validations for your parameters,
+  ensuring that they meet specific requirements before being passed to your controller actions.
+  Additionally, Pastore allows you to easily control access to your actions,
+  ensuring that only authorized users can access sensitive information.
+  With its intuitive interface and robust features,
+  Pastore is a must-have tool for any Rails developer looking to improve
+  the security and reliability of their application.
+email:
+- developers@opinioni.net
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".rspec"
+- ".rubocop.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Gemfile
+- Gemfile.lock
+- LICENSE
+- README.md
+- Rakefile
+- lib/pastore.rb
+- lib/pastore/guards.rb
+- lib/pastore/params_validators.rb
+- lib/pastore/version.rb
+homepage: https://github.com/demetra-it/pastore
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/demetra-it/pastore
+  source_code_uri: https://github.com/demetra-it/pastore
+  changelog_uri: https://github.com/demetra-it/pastore/blob/master/CHANGELOG.md
+  rubygems_mfa_required: 'true'
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.6.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.3.7
+signing_key: 
+specification_version: 4
+summary: A powerful gem for Rails that simplifies the process of validating parameters
+  and controlling access to actions in your controllers.
+test_files: []