Next refresh should show more results. ( run in 1.449 )
view release on metacpan or search on metacpan
lib/CAM/App.pm view on Meta::CPAN
=item authenticate
Test the login information, if any. Currently no tests are performed
-- this is a no-op. Subclasses may override this method to test login
credentials. Even though it's currently trivial, subclass methods
should alway include the line:
return undef if (!$self->SUPER::authenticate());
In case the parent authenticate() method adds a test in the future.
view release on metacpan or search on metacpan
my $protocol = lc($1);
my $host = $2;
my $path = $3;
# Strip off user and password, if any
my $credentials;
if ($host =~ /^(.*)\@([^\@]*)$/) {
$credentials = $1;
$host = lc($2);
} else {
$host = lc($host);
}
view release on metacpan or search on metacpan
lib/CGI/Application/Plugin/Authentication/Driver/CDBI.pm view on Meta::CPAN
FIELD_METHODS supports filters as specified by
CGI::Application::Plugin::Authentication::Driver
=head1 METHODS
=head2 verify_credentials
This method will test the provided credentials against the values found in
the database, according to the Driver configuration.
=cut
sub verify_credentials {
my $self = shift;
my @creds = @_;
my @_options=$self->options;
die "The Class::DBI driver requires a hash of options" if @_options % 2;
view release on metacpan or search on metacpan
lib/CGI/Authen/Simple.pm view on Meta::CPAN
my $auth = CGI::Authen::Simple->new();
$auth->logged_in() || $auth->auth();
# do stuff here
# if you need it, you can access the user's credentials like so:
my $username = $auth->{'profile'}->{'username'};
# assume your account table had other attributes, like full_name char(64)
my $fullname = $auth->{'profile'}->{'full_name'};
view release on metacpan or search on metacpan
=head2 REMINDER
CGI::Authent doesn't validate the passwords. It cannot even see them. It
just does a few tests and if the tests fail it sends to the user a
request for authentication. But it's the server's task to validate the
credentials passed by the browser.
If you want for example to validate passwords against a database,
consult your servers documentation. You will probably have to install some filter or plugin.
It should be relatively easy to find such beasts on the net. I've written an ISAPI filter for this,
you may get it at http://jenda.krynicky.cz/authfilter.1.0.zip . Take it as an example, not as a solution!
view release on metacpan or search on metacpan
lib/CGI/Ex/Auth.pm view on Meta::CPAN
$self->no_cookies_print;
return;
}
}
# oh - you're still here - well then - ask for login credentials
my $key_r = $self->key_redirect;
local $form->{$key_r} = $form->{$key_r} || $self->script_name . $self->path_info . (scalar(keys %$form) ? "?".$self->cgix->make_form($form) : '');
local $form->{'had_form_data'} = $args->{'had_form_data'} || 0;
$self->login_print;
my $data = $self->last_auth_data;
eval { die defined($data) ? $data : "Requesting credentials" };
# allow for a sleep to help prevent brute force
sleep($self->failed_sleep) if defined($data) && $data->error ne 'Login expired' && $self->failed_sleep;
$self->failure_hook;
view release on metacpan or search on metacpan
###########################################################
sub _login {
##
## check login credentials and load user profile
##
my $self = shift;
my ($username, $password) = @_;
view release on metacpan or search on metacpan
lib/CGI/Tiny/Cookbook.pod view on Meta::CPAN
}
};
=head2 Sessions
Regardless of the session mechanism, login credentials should only be sent over
HTTPS, and passwords should be stored on the server using a secure one-way
hash, such as with L<Crypt::Passphrase>.
L<Basic authentication|https://en.wikipedia.org/wiki/Basic_access_authentication>
has historically been used to provide a simplistic login session mechanism
which relies on the client to send the credentials with every subsequent
request in that browser session. However, it does not have a reliable logout or
session expiration mechanism.
Basic authentication can be handled by the CGI server itself (e.g.
L<Apache|https://httpd.apache.org/docs/2.4/howto/auth.html>), which restricts
view release on metacpan or search on metacpan
share/v3.json view on Meta::CPAN
"303": {
"description": "duplicate report",
"schema": { "$ref": "#/definitions/Error" }
},
"401": {
"description": "invalid credentials",
"schema": { "$ref": "#/definitions/Error" }
},
"400": {
"description": "report contains errors",
"schema": { "$ref": "#/definitions/Error" }
view release on metacpan or search on metacpan
lib/CPAN/Testers/Metabase/AWS.pm view on Meta::CPAN
namespace: prod
=head1 DESCRIPTION
This class instantiates a Metabase backend on the S3 and SimpleDB Amazon
Web Services (AWS). It uses L<Net::Amazon::Config> to provide user credentials
and the L<Metabase::Gateway> Role to provide actual functionality. As such,
it is mostly glue to get the right credentials to setup AWS clients and provide
them with standard resource names.
For example, given the C<<< bucket >>> "example" and the C<<< namespace >>> "alpha",
the following resource names would be used:
view release on metacpan or search on metacpan
vhost/cgi-bin/templates/users/user-login-author.html view on Meta::CPAN
<p>I'm sorry but that login was not recognised. Please try again, ensuring you
enter the correct email address and password. Thank you.
[% ELSE %]<p>[% errmess %]</p>
[% END %]
<p>If you are an author, please login using your standard PAUSE credentials.
You will then be able to browse your distributions and mark the appropriate
reports, which you believe to have been made in error.</p>
<p>In the interests of security, your PAUSE credentials will be used to
dynamically verify you are an author by PAUSE directly. Once successfully
verified, your PAUSE ID only is then held for the duration of the current
session, and deleted when the current session times out.<p>
<p>Please note that for those authors who are testers as well as authors,
view release on metacpan or search on metacpan
t/data/61daily.eml view on Meta::CPAN
If you have an issue with a particular report, or wish to gain further information from the tester, please use the 'Find A Tester' tool at http://stats.cpantesters.org/cpanmail.html, using the ID or GUID of the report, as listed above, to locate the ...
You can also adjust the frequency and nature of these notifications or unsubscribe from the notifications entirely, by going to the CPAN Testers Preferences website (https://prefs.cpantesters.org) and login with your PAUSE credentials. You can disabl...
Thanks,
The CPAN Testers
--
Reports: http://www.cpantesters.org
view release on metacpan or search on metacpan
0.010 2023-01-24 17:14:30+01:00 Europe/Amsterdam
- Assume Term::ReadKey is always present
- Add missing documentation for new_from_config_or_stdin
0.009 2018-12-16 16:31:13+01:00 Europe/Amsterdam
- Add fallback to ask for credentials on command line
0.008 2018-05-02 20:28:36+02:00 Europe/Amsterdam
- Add ?ACTION=add_uri to PAUSE upload URI
0.007 2018-04-23 13:12:48+02:00 Europe/Amsterdam
view release on metacpan or search on metacpan
lib/CPAN/FTP.pm view on Meta::CPAN
} else {
$CPAN::Frontend->mywarn(" Could not determine host from http_proxy '$http_proxy'\n");
}
if ($want_proxy) {
my($user, $pass) =
CPAN::HTTP::Credentials->get_proxy_credentials();
$ret = {
proxy_user => $user,
proxy_pass => $pass,
http_proxy => $http_proxy
};
view release on metacpan or search on metacpan
The CPM functionality is completely defined by its configuration file (config.xml) that acts also, as firmware of the module.
=head1 Configuration sample
The CPM needs a default configuration file that must be adjusted by the user, at least, including his credentials (valid user in MyPrinterCloud).
<?xml version="1.0" encoding="UTF-8"?>
<opt call="http://myprintercloud.nubeprint.com/np/selector.pl" proxy="" >
<id comm="call"
date="2010-09-10"
view release on metacpan or search on metacpan
lib/Cal/DAV.pm view on Meta::CPAN
for (qw(user pass url)) {
die "You must pass in a $_ param\n" unless defined $args{$_};
$opts{"-${_}"} = $args{$_};
}
my $dav = HTTP::DAV->new;
$dav->credentials(%opts);
return bless { _dav => $dav, url => $args{url}, _auto_commit => $args{auto_commit} }, $class;
}
=head2 parse <arg[s]>
view release on metacpan or search on metacpan
lib/Captive/Portal/Role/AuthenSimple.pm view on Meta::CPAN
return 1;
}
=item $capo->authenticate($username, $password)
Call the authenticator object with credentials. Returns true on success and false on failure.
=cut
sub authenticate {
my $self = shift;
view release on metacpan or search on metacpan
lib/Carp/Proxy.pm view on Meta::CPAN
Underscores are replaced by single spaces everywhere they occur. Spaces
are inserted everywhere character-case changes from lower to upper, and
upper-case characters are folded to lower-case. The following are example
conversions:
'no_user_credentials' => 'no user credentials'
'nonexistentRecord' => 'nonexistent record'
Sub-class B<Carp::Proxy> and override B<identifier_presentation()> if
you want a different convention.
view release on metacpan or search on metacpan
lib/Cassandra/Lite.pm view on Meta::CPAN
sub _login {
my $self = shift;
my $client = shift;
my $auth = Cassandra::AuthenticationRequest->new;
$auth->{credentials} = {username => $self->username, password => $self->password};
$client->login($auth);
}
sub _trigger_keyspace {
my ($self, $keyspace) = @_;
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/Authen/Simple.pm view on Meta::CPAN
#################### main pod documentation begin ###################
=head1 NAME
Catalyst::Authentication::Credential::Authen::Simple - Verify credentials with the Authen::Simple framework
=head1 SYNOPSIS
use Catalyst qw(Authentication);
# later on ...
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/CAS.pm view on Meta::CPAN
=item B<authenticate( $authinfo, $realm, $c )>
This is called during the normal Catalyst authentication process
and should never be called directly.
Since CAS is a service that verifies credentials outside of your
application, the login process for your application will have
two phases. In the first phase, an unauthenticated user will
attempt to access your application and be redirected to the CAS
for credential verification. A service URI must be provided to
the CAS so that once the user has been identified, they can be