rbac_system 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: 5a3c2341acf52bc0324e7e9ddcf70b59657974ae964e836fd78a8fc228aab014
4
+ data.tar.gz: 1b9215b92ca6dd5c4200efcfb912d927144b91d5f48186fd5f4b72e7f44115d1
5
+ SHA512:
6
+ metadata.gz: f0c0dc3c5ea8112687d155ac73df76a103543e5b90506402cee91b968bda6890a47cb78a0a888fc4d4299661220ac60d35954eda34e5c98849b9333a30f43ac7
7
+ data.tar.gz: 8bf9ee8b3b701efb74b01f55babae92e31e424e8011a4457bd37f29730c8315161cb2001163b3ee7f59b82cd0931d081c96309b12b4e53f75b6045ebec2df01d
data/.rspec ADDED
@@ -0,0 +1,3 @@
1
+ --format documentation
2
+ --color
3
+ --require spec_helper
data/.rubocop.yml ADDED
@@ -0,0 +1,8 @@
1
+ AllCops:
2
+ TargetRubyVersion: 3.0
3
+
4
+ Style/StringLiterals:
5
+ EnforcedStyle: double_quotes
6
+
7
+ Style/StringLiteralsInInterpolation:
8
+ EnforcedStyle: double_quotes
data/CHANGELOG.md ADDED
@@ -0,0 +1,5 @@
1
+ ## [Unreleased]
2
+
3
+ ## [0.1.0] - 2024-10-09
4
+
5
+ - Initial release
@@ -0,0 +1,132 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ We as members, contributors, and leaders pledge to make participation in our
6
+ community a harassment-free experience for everyone, regardless of age, body
7
+ size, visible or invisible disability, ethnicity, sex characteristics, gender
8
+ identity and expression, level of experience, education, socio-economic status,
9
+ nationality, personal appearance, race, caste, color, religion, or sexual
10
+ identity and orientation.
11
+
12
+ We pledge to act and interact in ways that contribute to an open, welcoming,
13
+ diverse, inclusive, and healthy community.
14
+
15
+ ## Our Standards
16
+
17
+ Examples of behavior that contributes to a positive environment for our
18
+ community include:
19
+
20
+ * Demonstrating empathy and kindness toward other people
21
+ * Being respectful of differing opinions, viewpoints, and experiences
22
+ * Giving and gracefully accepting constructive feedback
23
+ * Accepting responsibility and apologizing to those affected by our mistakes,
24
+ and learning from the experience
25
+ * Focusing on what is best not just for us as individuals, but for the overall
26
+ community
27
+
28
+ Examples of unacceptable behavior include:
29
+
30
+ * The use of sexualized language or imagery, and sexual attention or advances of
31
+ any kind
32
+ * Trolling, insulting or derogatory comments, and personal or political attacks
33
+ * Public or private harassment
34
+ * Publishing others' private information, such as a physical or email address,
35
+ without their explicit permission
36
+ * Other conduct which could reasonably be considered inappropriate in a
37
+ professional setting
38
+
39
+ ## Enforcement Responsibilities
40
+
41
+ Community leaders are responsible for clarifying and enforcing our standards of
42
+ acceptable behavior and will take appropriate and fair corrective action in
43
+ response to any behavior that they deem inappropriate, threatening, offensive,
44
+ or harmful.
45
+
46
+ Community leaders have the right and responsibility to remove, edit, or reject
47
+ comments, commits, code, wiki edits, issues, and other contributions that are
48
+ not aligned to this Code of Conduct, and will communicate reasons for moderation
49
+ decisions when appropriate.
50
+
51
+ ## Scope
52
+
53
+ This Code of Conduct applies within all community spaces, and also applies when
54
+ an individual is officially representing the community in public spaces.
55
+ Examples of representing our community include using an official email address,
56
+ posting via an official social media account, or acting as an appointed
57
+ representative at an online or offline event.
58
+
59
+ ## Enforcement
60
+
61
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
62
+ reported to the community leaders responsible for enforcement at
63
+ [INSERT CONTACT METHOD].
64
+ All complaints will be reviewed and investigated promptly and fairly.
65
+
66
+ All community leaders are obligated to respect the privacy and security of the
67
+ reporter of any incident.
68
+
69
+ ## Enforcement Guidelines
70
+
71
+ Community leaders will follow these Community Impact Guidelines in determining
72
+ the consequences for any action they deem in violation of this Code of Conduct:
73
+
74
+ ### 1. Correction
75
+
76
+ **Community Impact**: Use of inappropriate language or other behavior deemed
77
+ unprofessional or unwelcome in the community.
78
+
79
+ **Consequence**: A private, written warning from community leaders, providing
80
+ clarity around the nature of the violation and an explanation of why the
81
+ behavior was inappropriate. A public apology may be requested.
82
+
83
+ ### 2. Warning
84
+
85
+ **Community Impact**: A violation through a single incident or series of
86
+ actions.
87
+
88
+ **Consequence**: A warning with consequences for continued behavior. No
89
+ interaction with the people involved, including unsolicited interaction with
90
+ those enforcing the Code of Conduct, for a specified period of time. This
91
+ includes avoiding interactions in community spaces as well as external channels
92
+ like social media. Violating these terms may lead to a temporary or permanent
93
+ ban.
94
+
95
+ ### 3. Temporary Ban
96
+
97
+ **Community Impact**: A serious violation of community standards, including
98
+ sustained inappropriate behavior.
99
+
100
+ **Consequence**: A temporary ban from any sort of interaction or public
101
+ communication with the community for a specified period of time. No public or
102
+ private interaction with the people involved, including unsolicited interaction
103
+ with those enforcing the Code of Conduct, is allowed during this period.
104
+ Violating these terms may lead to a permanent ban.
105
+
106
+ ### 4. Permanent Ban
107
+
108
+ **Community Impact**: Demonstrating a pattern of violation of community
109
+ standards, including sustained inappropriate behavior, harassment of an
110
+ individual, or aggression toward or disparagement of classes of individuals.
111
+
112
+ **Consequence**: A permanent ban from any sort of public interaction within the
113
+ community.
114
+
115
+ ## Attribution
116
+
117
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118
+ version 2.1, available at
119
+ [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120
+
121
+ Community Impact Guidelines were inspired by
122
+ [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123
+
124
+ For answers to common questions about this code of conduct, see the FAQ at
125
+ [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126
+ [https://www.contributor-covenant.org/translations][translations].
127
+
128
+ [homepage]: https://www.contributor-covenant.org
129
+ [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130
+ [Mozilla CoC]: https://github.com/mozilla/diversity
131
+ [FAQ]: https://www.contributor-covenant.org/faq
132
+ [translations]: https://www.contributor-covenant.org/translations
data/LICENSE.txt ADDED
@@ -0,0 +1,21 @@
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) 2024 Yarramreddy.Sainathreddy@flaerhomes.com
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in
13
+ all copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21
+ THE SOFTWARE.
data/README.md ADDED
@@ -0,0 +1,151 @@
1
+ ## RbacSystem
2
+
3
+ The `rbac_system` gem provides a robust Role-Based Access Control (RBAC) implementation, enabling you to efficiently manage admin roles and permissions within your application. With this gem, you can easily define and enforce authorization rules for various resources and actions.
4
+
5
+ ## Overview
6
+
7
+ This gem allows you to define three primary entities:
8
+
9
+ 1. **Admin**: Represents your admin users and their basic details.
10
+ 2. **Role**: Defines roles with specific permissions.
11
+
12
+ - **Name**: The name of the role (e.g., `Editor`, `Viewer`).
13
+ - **Permissions**: A hash mapping resources to their respective actions. For example:
14
+
15
+ ```ruby
16
+ {
17
+ Upload: { manage: true, create: true },
18
+ Download: { manage: true, read: true },
19
+ Area: { manage: true, create: true, update: true, read: true },
20
+ City: { manage: true, create: true, update: true, read: true },
21
+ AccountLedger: { manage: true, read: true },
22
+ CouponDiscount: { manage: true, read: true, create: true, update: true }
23
+ }
24
+ ```
25
+
26
+ In this example, `Upload` and `Download` are custom resource names, while `Area`, `City`, etc., correspond to database models.
27
+
28
+ 3. **AdminRole**: A junction table that connects `Admin` and `Role` entities, allowing you to assign roles to admins.
29
+
30
+ ## Installation
31
+
32
+ To install the gem, add it to your application's Gemfile:
33
+
34
+ ```bash
35
+ bundle add rbac_system
36
+ ```
37
+
38
+ If bundler is not being used to manage dependencies, install the gem by executing:
39
+
40
+ ```bash
41
+ gem install rbac_system
42
+ ```
43
+
44
+ ## Usage
45
+
46
+ To use the rbac_system gem, you need to check authorization based on the current admin, the action being performed, and the resource name. Here are some usage scenarios:
47
+
48
+ Case 1: Model Exists in Database
49
+ For a standard model, you can implement authorization as follows:
50
+
51
+ before_action :check_authorization
52
+
53
+ action_map = {
54
+ 'create_area' => 'create',
55
+ 'area_listing' => 'read',
56
+ 'update_area' => 'update'
57
+ }
58
+
59
+ action = action_map[action_name]
60
+ resource = controller_name.classify
61
+
62
+ authorized = RbacSystem::Authorization.new(admin, resource, action).authorized?
63
+
64
+ unless authorized
65
+ render json: { status: 'failure', message: 'Forbidden', errors: ['You are not authorized to perform this action'] }, status: :forbidden
66
+ end
67
+
68
+ Multiple Models in a Single Controller
69
+ If your controller manages multiple models, use the following approach:
70
+
71
+ action_map = {
72
+ 'add_update_cart' => { action: 'create', resource: 'Cart' },
73
+ 'cart_checkout' => { action: 'create', resource: 'Cart' },
74
+ 'validate_discount' => { action: 'create', resource: 'Cart' },
75
+ 'get_cart_summary' => { action: 'read', resource: 'Cart' },
76
+ 'place_order' => { action: 'create', resource: 'Order' },
77
+ 'order_deliver' => { action: 'read', resource: 'Order' },
78
+ 'clear_cart' => { action: 'put', resource: 'Cart' },
79
+ 'get_orders' => { action: 'read', resource: 'Order' },
80
+ 'get_carts' => { action: 'read', resource: 'Cart' },
81
+ 'verify_unicommerce_order_status' => { action: 'update', resource: 'Order' },
82
+ 'unicommerce_snapshot' => { action: 'read', resource: 'ProductSku' },
83
+ 'cancel_order' => { action: 'create', resource: 'Order' },
84
+ 'get_unicommerce_order_status' => { action: 'read', resource: 'Order' }
85
+ }
86
+
87
+ action_info = action_map[action_name]
88
+ action = action_info[:action]
89
+ resource = action_info[:resource]
90
+
91
+ authorized = RbacSystem::Authorization.new(admin, resource, action).authorized?
92
+
93
+ unless authorized
94
+ render json: { status: 'failure', message: 'Forbidden', errors: ['You are not authorized to perform this action'] }, status: :forbidden
95
+ end
96
+
97
+ Custom Resource Names
98
+ If you need to define custom resource names without a corresponding model, you can do this:
99
+
100
+ ruby
101
+ Copy code
102
+ action_map = {
103
+ 'bulk_sku_upload' => 'create',
104
+ 'bulk_option_values_upload' => 'create',
105
+ 'bulk_option_value_sku_mappings_upload' => 'create',
106
+ 'bulk_product_medias_upload' => 'create'
107
+ }
108
+
109
+ action = action_map[action_name]
110
+ resource = 'Upload'
111
+
112
+ authorized = RbacSystem::Authorization.new(admin, resource, action).authorized?
113
+
114
+ unless authorized
115
+ render json: { status: 'failure', message: 'Forbidden', errors: ['You are not authorized to perform this action'] }, status: :forbidden
116
+ end
117
+
118
+ ## Development
119
+
120
+ After checking out the repository, run bin/setup to install dependencies. You can run tests with:
121
+ rake spec
122
+
123
+ For an interactive prompt to experiment, run:
124
+ bin/console
125
+
126
+ To install the gem onto your local machine, execute:
127
+
128
+ bundle exec rake install
129
+
130
+ To release a new version, update the version number in version.rb, and then run:
131
+ bundle exec rake release
132
+
133
+ This will create a Git tag for the version, push Git commits and the created tag, and push the .gem file to RubyGems.org.
134
+
135
+ ## Contributing
136
+
137
+ Bug reports and pull requests are welcome on GitHub at https://github.com/saiganiankoji/rbac_system. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Code of Conduct.
138
+
139
+ ## License
140
+
141
+ The gem is available as open source under the terms of the MIT License.
142
+
143
+ ## Code of Conduct
144
+
145
+ ### Key Improvements:
146
+
147
+ 1. **Clarity and Structure**: The README is structured into clear sections with headings, making it easy to navigate.
148
+ 2. **Comprehensive Usage Instructions**: Each usage case is explained with code examples, making it easy for users to understand how to implement the gem.
149
+ 3. **Development and Contributing Guidelines**: Clear instructions for development, contributing, and licensing provide users with the necessary information to participate in the project.
150
+
151
+ Feel free to customize any sections as needed, especially the GitHub links and any specific details regarding your implementation!
data/Rakefile ADDED
@@ -0,0 +1,12 @@
1
+ # frozen_string_literal: true
2
+
3
+ require "bundler/gem_tasks"
4
+ require "rspec/core/rake_task"
5
+
6
+ RSpec::Core::RakeTask.new(:spec)
7
+
8
+ require "rubocop/rake_task"
9
+
10
+ RuboCop::RakeTask.new
11
+
12
+ task default: %i[spec rubocop]
@@ -0,0 +1,28 @@
1
+ # frozen_string_literal: true
2
+ module RbacSystem
3
+ class Authorization
4
+ def initialize(admin, resource, action)
5
+ @admin = admin
6
+ @resource = resource
7
+ @action = action
8
+ end
9
+
10
+ def authorized?
11
+ roles.each do |role|
12
+ return true if role_authorized?(role)
13
+ end
14
+ false
15
+ end
16
+
17
+ private
18
+
19
+ def roles
20
+ @admin.roles
21
+ end
22
+
23
+ def role_authorized?(role)
24
+ role.permissions[@resource]&.key?(@action)
25
+ end
26
+ end
27
+ end
28
+
@@ -0,0 +1,5 @@
1
+ # frozen_string_literal: true
2
+
3
+ module RbacSystem
4
+ VERSION = "0.1.0"
5
+ end
@@ -0,0 +1,9 @@
1
+ # frozen_string_literal: true
2
+
3
+ require_relative "rbac_system/version"
4
+ require_relative "rbac_system/authorization"
5
+
6
+ module RbacSystem
7
+ class Error < StandardError; end
8
+ # Your code goes here...
9
+ end
@@ -0,0 +1,4 @@
1
+ module RbacSystem
2
+ VERSION: String
3
+ # See the writing guide of rbs: https://github.com/ruby/rbs#guides
4
+ end
metadata ADDED
@@ -0,0 +1,58 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: rbac_system
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.1.0
5
+ platform: ruby
6
+ authors:
7
+ - yarramsaireddy2001@gmail.com
8
+ autorequire:
9
+ bindir: exe
10
+ cert_chain: []
11
+ date: 2024-10-10 00:00:00.000000000 Z
12
+ dependencies: []
13
+ description: This gem provides a Role-Based Access Control implementation for Ruby
14
+ applications, allowing developers to define roles and permissions easily.
15
+ email:
16
+ - yarramsaireddy2001@gmail.com
17
+ executables: []
18
+ extensions: []
19
+ extra_rdoc_files: []
20
+ files:
21
+ - ".rspec"
22
+ - ".rubocop.yml"
23
+ - CHANGELOG.md
24
+ - CODE_OF_CONDUCT.md
25
+ - LICENSE.txt
26
+ - README.md
27
+ - Rakefile
28
+ - lib/rbac_system.rb
29
+ - lib/rbac_system/authorization.rb
30
+ - lib/rbac_system/version.rb
31
+ - sig/rbac_system.rbs
32
+ homepage: https://github.com/saiganiankoji/rbac_system
33
+ licenses:
34
+ - MIT
35
+ metadata:
36
+ allowed_push_host: https://rubygems.org
37
+ homepage_uri: https://github.com/saiganiankoji/rbac_system
38
+ source_code_uri: https://github.com/saiganiankoji/rbac_system
39
+ post_install_message:
40
+ rdoc_options: []
41
+ require_paths:
42
+ - lib
43
+ required_ruby_version: !ruby/object:Gem::Requirement
44
+ requirements:
45
+ - - ">="
46
+ - !ruby/object:Gem::Version
47
+ version: 3.0.0
48
+ required_rubygems_version: !ruby/object:Gem::Requirement
49
+ requirements:
50
+ - - ">="
51
+ - !ruby/object:Gem::Version
52
+ version: '0'
53
+ requirements: []
54
+ rubygems_version: 3.3.3
55
+ signing_key:
56
+ specification_version: 4
57
+ summary: A simple RBAC system for Ruby applications
58
+ test_files: []