view release on metacpan or search on metacpan
lib/CPAN/Maker.pm view on Meta::CPAN
Example:
version: 1.8.0
project:
git: https://github.com/rlauer6/perl-Amazon-Credentials
description: "AWS credentials discoverer"
author:
name: Rob Lauer
mailto: rlauer6@comcast.net
pm_module: Amazon::Credentials
include-version: no
view release on metacpan or search on metacpan
data/tiddlers.json view on Meta::CPAN
"title": "UserInput",
"modified": "20250717072807326",
"created": "20230725010759791"
},
{
"text": "\"\"\"\no See also:\n- Acronyms - for 2FA\n- [[CPAN]]\n- DatabaseAndSQL\n- DataTraversal\n- GitStuff\n- WebServices\n- https://openid.net/developers/how-connect-works/ - for OpenID Connect\n- https://savage.net.au/misc/Digital.Securi...
"title": "UsernamePassword",
"modified": "20260325062917773",
"created": "20240208003631502"
},
{
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:
lib/CPAN/Testers/Metabase/AWS.pm view on Meta::CPAN
domain for indexing.
=item *
C<<< amazon_config >>> -- optional -- a L<Net::Amazon::Config> object containing
Amazon Web Service credentials. If not provided, one will be created using
the default location for the config file.
=item *
C<<< profile_name >>> -- optional -- the name of a profile for use with
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
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
0.006 2018-04-23 11:55:10+02:00 Europe/Amsterdam
- Re-add ExecDir to the dzil configuration
0.005 2018-04-19 16:58:28+02:00 Europe/Amsterdam
- Support reserved characters in credentials
- Improve error messages for internal errors
0.004 2017-05-14 12:30:44+02:00 Europe/Paris
- Fix user attribute name
view release on metacpan or search on metacpan
0.103006 2013-12-13 08:18:36 America/New_York
update bugtracker and repo metadata
0.103005 2013-07-01 19:01:17 America/New_York
Use Config::Identity to permit GPG-encrypting on-disk credentials
(thanks, Mike Doherty)
0.103004 2013-03-12 15:51:43 America/New_York
like 0.103003, but a production release
view release on metacpan or search on metacpan
lib/CPAN/Audit/DB.pm view on Meta::CPAN
use warnings;
our $VERSION = '20260419.002';
sub db {
{"dists" => {"ActivePerl" => {"advisories" => [{"affected_versions" => ["==5.16.1.1601"],"cves" => ["CVE-2012-5377"],"description" => "Untrusted search path vulnerability in the installation functionality in ActivePerl 5.16.1.1601, when installed in...
}
__PACKAGE__;
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.
lib/Carp/Proxy.pm view on Meta::CPAN
*** Please contact the maintainer ***
your.name@support.org 555-1212
*** Missing Handler ***
handler_name: no_credentials
handler_pkgs: main
handler_prefix: (undef)
*** Stacktrace ***
fatal called from line 443 of /usr/local/bin/hibs
view release on metacpan or search on metacpan
lib/Cassandra/Client/Connection.pm view on Meta::CPAN
sub authenticate {
my ($self, $callback, $initial_challenge)= @_;
my $authenticator= unpack_string($initial_challenge);
if (!$self->{options}{authentication}) {
return $callback->("Server expected authentication using <$authenticator> but no credentials were set");
}
my $auth;
eval {
$auth= $self->{options}{authentication}->begin($authenticator);
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 ...
lib/Catalyst/Authentication/Credential/Authen/Simple.pm view on Meta::CPAN
This module helps your Cataylst Application authenticate against a lot of credential databases thanks to the Authen::Simple framework.
=head1 USAGE
Just configure your Catalyst App Authentication to use class 'Authen::Simple' as the credential verifier, and give it a set of Authen::Simple classes. You can pass arguments to the Authen::Simple:XXX class constructors with the 'args' key. Note that ...
'Plugin::Authentication' => {
'realms' => {
'default' => {
'store' => { ... }
lib/Catalyst/Authentication/Credential/Authen/Simple.pm view on Meta::CPAN
=cut
=head2 authenticate
Usage : Call $c->authenticate({ username => ..., password => ...});
Returns : User object if the credentials are verified successfully. undef if user not authenticated.
=cut
=head1 AUTHOR
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
lib/Catalyst/Authentication/Credential/CAS.pm view on Meta::CPAN
C<'ticket'> key of the C<$authinfo> hash. If no ticket is
defined (phase one authentication) the response will be set to
redirect to the CAS and the current action will be detached.
You may also pass other parameters in the C<$authinfo> hash that
will affect the way the CAS verifies credentials. See the
documentation for L<Authen::CAS::Client|Authen::CAS::Client> for
more on the C<'renew'>, C<'gateway'> and C<'pgtUrl'> parameters.
=back
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/Facebook/OAuth2.pm view on Meta::CPAN
L<http://facebook.com> that will ask the user to confirm our request to
authenticate him. Once that has happened, Facebook will redirect back to use and
C<authenticate> will return a user instance.
Note how this is different from most other Catalyst authentication
credentials. Successful authentication requires two requests to the Catalyst
application - one is initiated by the user, the second one is caused by Facebook
redirecting the user back to the application.
Because of that, special care has to be taken. If C<authenticate> returns a
false value, that means it set up the appropriate redirect response in
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/Facebook.pm view on Meta::CPAN
if (my $user = $c->authenticate(undef,'facebook')) {
# user is logged in - redirect or do something
}
else {
# user has no account in your system
# detect Facebook credentials and create an account
# or do comething else
}
}
=head1 DESCRIPTION
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/HTTP/Proxy.pm view on Meta::CPAN
my $headers = $c->req->headers;
if ( my ( $user, $password ) = $headers->authorization_basic ) {
my $ua = Catalyst::Authentication::Credential::HTTP::Proxy::User->new;
$ua->credentials($user, $password);
my $resp = $ua->get($self->url);
if ( $resp->is_success ) {
# Config username_field TODO
my $user_obj = $realm->find_user( { username => $user }, $c);
unless ($user_obj) {
lib/Catalyst/Authentication/Credential/HTTP/Proxy.pm view on Meta::CPAN
$c->log->info('Remote authentication failed:'.$resp->message);
return 0;
}
}
elsif ( $c->debug ) {
$c->log->info('No credentials provided for basic auth');
return 0;
}
}
1;
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/HTTP.pm view on Meta::CPAN
If this is omitted or its value is empty, the client will assume that the
protection space consists of all URIs on the responding server.
Therefore, if your application is not hosted at the root of this domain, and you want to
prevent the authentication credentials for this application being sent to any other applications.
then you should use the I<use_uri_for> configuration option, and pass a domain of I</>.
=back
=item authenticate_basic $c, $realm, \%auth_info
lib/Catalyst/Authentication/Credential/HTTP.pm view on Meta::CPAN
=item use_uri_for
If this configuration key has a true value, then the domain(s) for the authorization header will be
run through $c->uri_for(). Use this configuration option if your application is not running at the root
of your domain, and you want to ensure that authentication credentials from your application are not shared with
other applications on the same server.
=item require_ssl
If this configuration key has a true value then authentication will be denied
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/OpenID.pm view on Meta::CPAN
As previously noted, L</EXTENSIONS TO OPENID>, I have not tested the extensions. I would be grateful for any feedback or, better, tests.
=head2 FATALS
The problems encountered by failed OpenID operations have always been fatals in the past. This is unexpected behavior for most users as it differs from other credentials. Authentication errors here are no longer fatal. Debug/error output is improved ...
=head1 SYNOPSIS
In MyApp.pm-
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/RemoteHTTP.pm view on Meta::CPAN
keep_alive => $self->http_keep_alive ? 1 : 0 );
# add prefix/suffix to user data to make auth_user, get password
my $auth_user = sprintf( '%s%s%s', $self->user_prefix, $username, $self->user_suffix );
my $password = $authinfo->{ $self->password_field };
$ua->set_credentials( $auth_user, $password );
# do the request
my $res = $ua->head( $self->url );
# did it succeed
lib/Catalyst/Authentication/Credential/RemoteHTTP.pm view on Meta::CPAN
=item url
The URL that is used to authenticate the user. The module attempts
to fetch this URL using a HEAD request (to prevent dragging a large
page across the network) with the credentials given. If this fails
then the authentication fails. If no URL is supplied in the config,
then an exception is thrown on startup.
=item username_field
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/Twitter.pm view on Meta::CPAN
# get the user
$self->_twitter->access_token($access_token);
$self->_twitter->access_token_secret($access_token_secret);
my $twitter_user_hash = eval {
$self->_twitter->verify_credentials;
};
if ($@ || !$twitter_user_hash) {
$c->log->debug("no twitter_user_hash or error: ".$@);
return undef;
lib/Catalyst/Authentication/Credential/Twitter.pm view on Meta::CPAN
# user has an account - redirect or do something cool
$c->res->redirect("/super/secret/member/area");
}
else {
# user doesn't have an account - either detect Twitter
# credentials and create one, or return an error.
#
# Note that "request_token" and "request_token_secret"
# are stored in $c->user_session as hashref variables under
# the same names
}
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Credential/Upstream/Headers.pm view on Meta::CPAN
package Catalyst::Authentication::Credential::Upstream::Headers;
{
$Catalyst::Authentication::Credential::Upstream::Headers::VERSION = '0.02';
}
# ABSTRACT: Catalyst authentication credentials from HTTP headers
use Moose;
has user_header =>
isa => 'Str',
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Realm/Adaptor.pm view on Meta::CPAN
The Catalyst::Authentication::Realm::Adaptor allows for modification of
authentication parameters within the catalyst application. It's basically a
filter used to adjust authentication parameters globally within the
application or to adjust user retrieval parameters provided by the credential
in order to be compatible with a different store. It provides for better
control over interaction between credentials and stores. This is particularly
useful when working with external authentication such as OpenID or OAuth.
__PACKAGE__->config(
'Plugin::Authentication' => {
'default' => {
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Store/LDAP.pm view on Meta::CPAN
wide variation of LDAP directories and schemas from one system to another.
It authenticates users in two steps:
1) A search of the directory is performed, looking for a user object that
matches the username you pass. This is done with the bind credentials
supplied in the "binddn" and "bindpw" configuration options.
2) If that object is found, we then re-bind to the directory as that object.
Assuming this is successful, the user is Authenticated.
view release on metacpan or search on metacpan
lib/Catalyst/Authentication/Store/UserXML.pm view on Meta::CPAN
}
},
'authentication' => {
'userxml' => {
'folder' => 'members',
'user_folder_file' => 'index.xml', # optional if credentials stored one per folder
}
},
);
# later in controller (login)
view release on metacpan or search on metacpan
inc/Test/WWW/Mechanize/Catalyst.pm view on Meta::CPAN
$self->_set_host_header($request);
my $res = $self->_check_external_request($request);
return $res if $res;
my @creds = $self->get_basic_credentials( "Basic", $uri );
$request->authorization_basic( @creds ) if @creds;
require Catalyst;
my $response = $Catalyst::VERSION >= 5.89000 ?
Catalyst::Test::_local_request($self->{catalyst_app}, $request) :