package Yancy::Plugin::Auth; our $VERSION = '1.081'; # ABSTRACT: Add one or more authentication plugins to your site #pod =head1 SYNOPSIS #pod #pod use Mojolicious::Lite; #pod plugin Yancy => { #pod backend => 'sqlite://myapp.db', #pod schema => { #pod users => { #pod properties => { #pod id => { type => 'integer', readOnly => 1 }, #pod plugin => { #pod type => 'string', #pod enum => [qw( password token )], #pod }, #pod username => { type => 'string' }, #pod # Optional password for Password auth #pod password => { type => 'string' }, #pod }, #pod }, #pod }, #pod }; #pod app->yancy->plugin( 'Auth' => { #pod schema => 'users', #pod username_field => 'username', #pod password_field => 'password', #pod plugin_field => 'plugin', #pod plugins => [ #pod [ #pod Password => { #pod password_digest => { #pod type => 'SHA-1', #pod }, #pod }, #pod ], #pod 'Token', #pod ], #pod } ); #pod #pod =head1 DESCRIPTION #pod #pod B This module is C and its API may change before #pod Yancy v2.000 is released. #pod #pod This plugin adds authentication to your site. #pod #pod Multiple authentication plugins can be added with this plugin. If you #pod only ever want to have one type of auth, you can use that auth plugin #pod directly if you want. #pod #pod This module composes the L role #pod to provide the #pod L #pod authorization method. #pod #pod =head1 CONFIGURATION #pod #pod This plugin has the following configuration options. #pod #pod =head2 schema #pod #pod The name of the Yancy schema that holds users. Required. #pod #pod =head2 username_field #pod #pod The name of the field in the schema which is the user's identifier. #pod This can be a user name, ID, or e-mail address, and is provided by the #pod user during login. #pod #pod =head2 password_field #pod #pod The name of the field to use for the password or secret. #pod #pod =head2 plugin_field #pod #pod The field to store which plugin the user is using to authenticate. This #pod field is only used if two auth plugins have the same username field. #pod #pod =head2 plugins #pod #pod An array of auth plugins to configure. Each plugin can be either a name #pod (in the C namespace) or an array reference with #pod two elements: The name (in the C namespace) and a #pod hash reference of configuration. #pod #pod Each of this module's configuration keys will be used as the default for #pod all the other auth plugins. Other plugins can override this #pod configuration individually. For example, users and tokens can be stored #pod in different schemas: #pod #pod app->yancy->plugin( 'Auth' => { #pod plugins => [ #pod [ #pod 'Password', #pod { #pod schema => 'users', #pod username_field => 'username', #pod password_field => 'password', #pod password_digest => { type => 'SHA-1' }, #pod }, #pod ], #pod [ #pod 'Token', #pod { #pod schema => 'tokens', #pod token_field => 'token', #pod }, #pod ], #pod ], #pod } ); #pod #pod =head2 Single User / Multiple Auth #pod #pod To allow a single user to configure multiple authentication mechanisms, do not #pod configure a C. Instead, give every authentication plugin its own #pod C. Then, once a user has registered with one auth method, they #pod can log in and register with another auth method to link to the same account. #pod #pod =head2 Sessions #pod #pod This module uses L #pod to store the login information in a secure, signed cookie. #pod #pod To configure the default expiration of a session, use #pod L. #pod #pod use Mojolicious::Lite; #pod # Expire a session after 1 day of inactivity #pod app->sessions->default_expiration( 24 * 60 * 60 ); #pod #pod =head1 HELPERS #pod #pod This plugin has the following helpers. #pod #pod =head2 yancy.auth.current_user #pod #pod Get the current user from one of the configured plugins, if any. Returns #pod C if no user was found in the session. #pod #pod my $user = $c->yancy->auth->current_user #pod || return $c->render( status => 401, text => 'Unauthorized' ); #pod #pod =head2 yancy.auth.require_user #pod #pod Validate there is a logged-in user and optionally that the user data has #pod certain values. See L. #pod #pod # Display the user dashboard, but only to logged-in users #pod my $auth_route = $app->routes->under( '/user', $app->yancy->auth->require_user ); #pod $auth_route->get( '' )->to( 'user#dashboard' ); #pod #pod =head2 yancy.auth.login_form #pod #pod Return an HTML string containing the rendered login forms for all #pod configured auth plugins, in order. #pod #pod %# Display a login form to an unauthenticated visitor #pod % if ( !$c->yancy->auth->current_user ) { #pod %= $c->yancy->auth->login_form #pod % } #pod #pod =head2 yancy.auth.logout #pod #pod Log out any current account from any auth plugin. Use this in your own #pod route handlers to perform a logout. #pod #pod =head1 ROUTES #pod #pod This plugin creates the following L. #pod Use named routes with helpers like #pod L, #pod L, and #pod L. #pod #pod =head2 yancy.auth.login_form #pod #pod Display all of the login forms for the configured auth plugins. This route handles C #pod requests and can be used with the L, #pod L, #pod and L helpers. #pod #pod %= link_to Login => 'yancy.auth.login_form' #pod <%= link_to 'yancy.auth.login_form', begin %>Login<% end %> #pod

Login here: <%= url_for 'yancy.auth.login_form' %>

#pod #pod =head2 yancy.auth.logout #pod #pod Log out of all configured auth plugins. This route handles C #pod requests and can be used with the L, #pod L, #pod and L helpers. #pod #pod %= link_to Logout => 'yancy.auth.logout' #pod <%= link_to 'yancy.auth.logout', begin %>Logout<% end %> #pod

Logout here: <%= url_for 'yancy.auth.logout' %>

#pod #pod =head1 TEMPLATES #pod #pod To override these templates, add your own at the designated path inside #pod your app's C directory. #pod #pod =head2 yancy/auth/login_form.html.ep #pod #pod This displays all of the login forms for all of the configured plugins #pod (if the plugin has a login form). #pod #pod =head2 yancy/auth/login_page.html.ep #pod #pod This displays the login form on a page directing the user to log in. #pod #pod =head2 layouts/yancy/auth.html.ep #pod #pod The layout that Yancy uses when displaying the login page, the #pod unauthorized error message, and other auth-related pages. #pod #pod =head1 SEE ALSO #pod #pod =head2 Multiplex Plugins #pod #pod These are possible Auth plugins that can be used with this plugin (or as #pod standalone, if desired). #pod #pod =over #pod #pod =item * L #pod #pod =item * L #pod #pod =item * L #pod #pod =item * L #pod #pod =back #pod #pod =cut use Mojo::Base 'Mojolicious::Plugin'; use Role::Tiny::With; with 'Yancy::Plugin::Auth::Role::RequireUser'; use Mojo::Loader qw( load_class ); use Yancy::Util qw( currym match ); has _plugins => sub { [] }; has route =>; has logout_route =>; sub register { my ( $self, $app, $config ) = @_; for my $plugin_conf ( @{ $config->{plugins} } ) { my $name; if ( !ref $plugin_conf ) { $name = $plugin_conf; $plugin_conf = {}; } else { ( $name, $plugin_conf ) = @$plugin_conf; } # If we got a route config, we need to customize the plugin # routes as well. If this plugin got its own "route" config, # use it. Otherwise, build a route from the auth route and the # plugin's moniker. if ( my $route = $app->yancy->routify( $config->{route} ) ) { $plugin_conf->{route} = $app->yancy->routify( $plugin_conf->{route}, $route->any( $plugin_conf->{moniker} || lc $name ), ); } my %merged_conf = ( %$config, %$plugin_conf ); if ( $plugin_conf->{username_field} ) { # If this plugin has a unique username field, we don't need # to specify a plugin field. This means a single user can # have multiple auth mechanisms. delete $merged_conf{ plugin_field }; } my $class = join '::', 'Yancy::Plugin::Auth', $name; if ( my $e = load_class( $class ) ) { die sprintf 'Unable to load auth plugin %s: %s', $name, $e; } my $plugin = $class->new( \%merged_conf ); push @{ $self->_plugins }, $plugin; # Plugin hashref overrides config from main Auth plugin $plugin->init( $app, \%merged_conf ); } $app->helper( 'yancy.auth.current_user' => currym( $self, 'current_user' ), ); $app->helper( 'yancy.auth.plugins' => currym( $self, 'plugins' ), ); $app->helper( 'yancy.auth.logout' => currym( $self, 'logout' ), ); $app->helper( 'yancy.auth.login_form' => currym( $self, 'login_form' ), ); # Make this route after all the plugin routes so that it matches # last. $self->route( $app->yancy->routify( $config->{route}, $app->routes->get( '/yancy/auth' ), ) ); $self->logout_route( $self->route->get( '/logout' )->to( cb => currym( $self, '_handle_logout' ) )->name( 'yancy.auth.logout' ) ); $self->route->get( '' )->to( cb => currym( $self, '_login_page' ) )->name( 'yancy.auth.login_form' ); } #pod =method current_user #pod #pod Returns the currently logged-in user, if any. #pod #pod =cut sub current_user { my ( $self, $c ) = @_; for my $plugin ( @{ $self->_plugins } ) { if ( my $user = $plugin->current_user( $c ) ) { return $user; } } return undef; } #pod =method plugins #pod #pod Returns the list of configured auth plugins. #pod #pod =cut sub plugins { my ( $self, $c ) = @_; return @{ $self->_plugins }; } #pod =method login_form #pod #pod %= $c->yancy->auth->login_form #pod #pod Return the rendered login form template. #pod #pod =cut sub login_form { my ( $self, $c ) = @_; return $c->render_to_string( template => 'yancy/auth/login_form', plugins => $self->_plugins, ); } sub _login_page { my ( $self, $c ) = @_; $c->render( template => 'yancy/auth/login_page', plugins => $self->_plugins, ); } #pod =method logout #pod #pod Log out the current user. Will call the C method on all configured auth plugins. #pod #pod =cut sub logout { my ( $self, $c ) = @_; $_->logout( $c ) for $self->plugins; } sub _handle_logout { my ( $self, $c ) = @_; $self->logout( $c ); $c->res->code( 303 ); my $redirect_to = $c->param( 'redirect_to' ) // $c->req->headers->referrer // '/'; if ( $redirect_to eq $c->req->url->path ) { $redirect_to = '/'; } return $c->redirect_to( $redirect_to ); } 1; __END__ =pod =head1 NAME Yancy::Plugin::Auth - Add one or more authentication plugins to your site =head1 VERSION version 1.081 =head1 SYNOPSIS use Mojolicious::Lite; plugin Yancy => { backend => 'sqlite://myapp.db', schema => { users => { properties => { id => { type => 'integer', readOnly => 1 }, plugin => { type => 'string', enum => [qw( password token )], }, username => { type => 'string' }, # Optional password for Password auth password => { type => 'string' }, }, }, }, }; app->yancy->plugin( 'Auth' => { schema => 'users', username_field => 'username', password_field => 'password', plugin_field => 'plugin', plugins => [ [ Password => { password_digest => { type => 'SHA-1', }, }, ], 'Token', ], } ); =head1 DESCRIPTION B This module is C and its API may change before Yancy v2.000 is released. This plugin adds authentication to your site. Multiple authentication plugins can be added with this plugin. If you only ever want to have one type of auth, you can use that auth plugin directly if you want. This module composes the L role to provide the L authorization method. =head1 METHODS =head2 current_user Returns the currently logged-in user, if any. =head2 plugins Returns the list of configured auth plugins. =head2 login_form %= $c->yancy->auth->login_form Return the rendered login form template. =head2 logout Log out the current user. Will call the C method on all configured auth plugins. =head1 CONFIGURATION This plugin has the following configuration options. =head2 schema The name of the Yancy schema that holds users. Required. =head2 username_field The name of the field in the schema which is the user's identifier. This can be a user name, ID, or e-mail address, and is provided by the user during login. =head2 password_field The name of the field to use for the password or secret. =head2 plugin_field The field to store which plugin the user is using to authenticate. This field is only used if two auth plugins have the same username field. =head2 plugins An array of auth plugins to configure. Each plugin can be either a name (in the C namespace) or an array reference with two elements: The name (in the C namespace) and a hash reference of configuration. Each of this module's configuration keys will be used as the default for all the other auth plugins. Other plugins can override this configuration individually. For example, users and tokens can be stored in different schemas: app->yancy->plugin( 'Auth' => { plugins => [ [ 'Password', { schema => 'users', username_field => 'username', password_field => 'password', password_digest => { type => 'SHA-1' }, }, ], [ 'Token', { schema => 'tokens', token_field => 'token', }, ], ], } ); =head2 Single User / Multiple Auth To allow a single user to configure multiple authentication mechanisms, do not configure a C. Instead, give every authentication plugin its own C. Then, once a user has registered with one auth method, they can log in and register with another auth method to link to the same account. =head2 Sessions This module uses L to store the login information in a secure, signed cookie. To configure the default expiration of a session, use L. use Mojolicious::Lite; # Expire a session after 1 day of inactivity app->sessions->default_expiration( 24 * 60 * 60 ); =head1 HELPERS This plugin has the following helpers. =head2 yancy.auth.current_user Get the current user from one of the configured plugins, if any. Returns C if no user was found in the session. my $user = $c->yancy->auth->current_user || return $c->render( status => 401, text => 'Unauthorized' ); =head2 yancy.auth.require_user Validate there is a logged-in user and optionally that the user data has certain values. See L. # Display the user dashboard, but only to logged-in users my $auth_route = $app->routes->under( '/user', $app->yancy->auth->require_user ); $auth_route->get( '' )->to( 'user#dashboard' ); =head2 yancy.auth.login_form Return an HTML string containing the rendered login forms for all configured auth plugins, in order. %# Display a login form to an unauthenticated visitor % if ( !$c->yancy->auth->current_user ) { %= $c->yancy->auth->login_form % } =head2 yancy.auth.logout Log out any current account from any auth plugin. Use this in your own route handlers to perform a logout. =head1 ROUTES This plugin creates the following L. Use named routes with helpers like L, L, and L. =head2 yancy.auth.login_form Display all of the login forms for the configured auth plugins. This route handles C requests and can be used with the L, L, and L helpers. %= link_to Login => 'yancy.auth.login_form' <%= link_to 'yancy.auth.login_form', begin %>Login<% end %>

Login here: <%= url_for 'yancy.auth.login_form' %>

=head2 yancy.auth.logout Log out of all configured auth plugins. This route handles C requests and can be used with the L, L, and L helpers. %= link_to Logout => 'yancy.auth.logout' <%= link_to 'yancy.auth.logout', begin %>Logout<% end %>

Logout here: <%= url_for 'yancy.auth.logout' %>

=head1 TEMPLATES To override these templates, add your own at the designated path inside your app's C directory. =head2 yancy/auth/login_form.html.ep This displays all of the login forms for all of the configured plugins (if the plugin has a login form). =head2 yancy/auth/login_page.html.ep This displays the login form on a page directing the user to log in. =head2 layouts/yancy/auth.html.ep The layout that Yancy uses when displaying the login page, the unauthorized error message, and other auth-related pages. =head1 SEE ALSO =head2 Multiplex Plugins These are possible Auth plugins that can be used with this plugin (or as standalone, if desired). =over =item * L =item * L =item * L =item * L =back =head1 AUTHOR Doug Bell =head1 COPYRIGHT AND LICENSE This software is copyright (c) 2021 by Doug Bell. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. =cut