kemal-authorizer v0.3.0
kemal-authorizer
This is a shard that makes it easy to make specific routes in a Kemal application only accessible to either anonymous, authenticated or authorized (administrators) users.
Installation
-
Add the dependency to your
shard.yml
:dependencies: kemal-authorizer: github: henrikac/kemal-authorizer
-
Run
shards install
Usage
require "kemal"
require "kemal-session"
require "kemal-authorizer"
Kemal::Session.config do |config|
config.secret = "some_secret"
end
# Only anonymous users can access these routes.
# authenticated users will be redirected to "/" (default route).
add_handler Kemal::Authorizer::AnonymousHandler.new({
"/login" => ["GET", "POST"],
"/signup" => ["GET", "POST"]
})
# Only authenticated users can access these routes.
# Unauthenticated users will be redirected to "/login?next=..." (default route).
add_handler Kemal::Authorizer::AuthenticationHandler.new({
"/dashboard" => ["GET"],
"/logout" => ["POST"]
})
# Only authenticated users that `is_admin` can access this route.
# Unauthenticated users will be redirected to "/login?next=..." (default route).
# If the user is authenticated but not an admin then the status code will be set to 401.
add_handler Kemal::Authorizer::AuthorizationHandler.new({
"/admin" => ["GET"]
})
get "/" do |env|
user = Kemal::Authorizer::UserStorableObject.new(1, "user@mail.com", true) # id, mail, is_admin
env.session.object("user", user)
"Home"
end
get "/login" do |env|
"Login"
end
get "/admin" do |env|
"Admin"
end
Kemal.run
Configuration
Kemal::Authorizer
has a few default configurations that can changed if needed.
Kemal::Authorizer.config do |config|
config.anonymous_url = "/"
config.login_url = "/login"
config.user_obj_name = "user" # name of the session object env.session.object(user_obj_name, obj)
config.user_type = Kemal::Authorizer::UserStorableObject
end
Custom Handlers
You can create custom handlers by inheriting from Kemal::Authorizer::BaseHandler
.
class CustomHandler < Kemal::Authorizer::BaseHandler
def call(context)
# add custom logic
call_next context
end
end
add_handler CustomHandler.new({"/my/route", ["GET", "POST", "PUT"]})
Custom StorableUser
If the built-in UserStorableObject
is not sufficient enough then it is possible to make a custom type and then set config.user_type
to the new type. New StorableUser types must inherit from Kemal::Authorizer::StorableUser
.
Kemal::Authorizer::StorableUser
is a class with a single property is_admin
that is set to false
by default.
require "json"
class MyStorableUserType < Kemal::Authorizer::StorableUser
include JSON::Serializable
include Kemal::Session::StorableObject
property id : Int32
property name : String
def initialize(@id : Int32, @name : String); end
end
# and then
Kemal::Authorizer.config do |config|
config.user_type = MyStorableUserType
end
user = MyStorableUserType.new(1, "Alice")
user.id # => 1
user.name # => Alice
user.is_admin # => false
Contributing
- Fork it (https://github.com/henrikac/kemal-authorizer/fork)
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create a new Pull Request
Contributors
- Henrik Christensen - creator and maintainer
kemal-authorizer
- 4
- 0
- 0
- 1
- 2
- over 3 years ago
- June 28, 2021
MIT License
Thu, 21 Nov 2024 09:52:46 GMT