Next refresh should show more results. ( run in 1.629 )
view release on metacpan or search on metacpan
lib/ClearPress/authenticator/db.pm view on Meta::CPAN
}
return $DEFAULT_CIPHER;
}
sub authen_credentials {
my ($self, $ref) = @_;
if(!$ref ||
!$ref->{username} ||
!$ref->{password} ) {
view all matches for this distribution
view release on metacpan or search on metacpan
lib/CCfnX/VagrantDeployer.pm view on Meta::CPAN
@lines = @{ $self->origin->Resource('Instance')->Properties->UserData->process_with_context($self->origin, \@lines) };
my $content = join '', @lines;
$content =~ s/\\/\\\\/;
warn "I'm extending a 900 second (15 min) token with you're actual credentials to vagrant";
my $creds = Paws::Credential::ProviderChain->new();
my $aws_access_key = $creds->access_key;
my $aws_secret_key = $creds->secret_key;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/CloudHealth/API.pm view on Meta::CPAN
has call_former => (is => 'ro', isa => HasMethods['params2request'], default => sub {
require CloudHealth::API::CallObjectFormer;
CloudHealth::API::CallObjectFormer->new;
});
has credentials => (is => 'ro', isa => HasMethods['api_key'], default => sub {
require CloudHealth::API::Credentials;
CloudHealth::API::Credentials->new;
});
has io => (is => 'ro', isa => HasMethods['call'], default => sub {
require CloudHealth::API::Caller;
view all matches for this distribution
view release on metacpan or search on metacpan
bin/cloudhealth view on Meta::CPAN
return $arg_parser->parse;
});
has argv => (is => 'ro', isa => ArrayRef, required => 1);
has ch => (is => 'ro', lazy => 1, default => sub { CloudHealth::API->new });
has credentials_detected => (is => 'ro', isa => Bool, lazy => 1, default => sub {
my $self = shift;
$self->ch->credentials->is_set;
});
has run_method => (is => 'ro', isa => Maybe[Str], lazy => 1, default => sub { shift->argv->[0] });
has method_specified => (is => 'ro', isa => Bool, lazy => 1, default => sub {
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Clustericious/Client.pm view on Meta::CPAN
has server_url => '';
has [qw(tx res userinfo ua )];
has _remote => ''; # Access via remote()
has _cache => sub { + {} }; # cache of credentials
sub client
{
carp "Clustericious::Client->client is deprecated (use ua instead)";
shift->ua(@_);
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Config/AWS.pm view on Meta::CPAN
list_profiles
read_file
read_string
read_handle
config_file
credentials_file
default_profile
);
our $VERSION = '0.12';
our %EXPORT_TAGS = (
ini => [qw( read_file read_string read_handle )],
aws => [qw( config_file default_profile credentials_file )],
read => [qw( read read_all list_profiles )],
all => [qw( :ini :aws :read )],
);
# Internal methods for parsing and validation
my $prepare = sub {
# Input is given argument or credentials file (if exists) or config file.
my $input = shift // do {
my $cred_file = credentials_file();
-r $cred_file ? $cred_file : config_file();
};
unless ( Ref::Util::is_ref $input ) {
require Path::Tiny;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Config/Model/models/Ssh/HostElement.pl view on Meta::CPAN
'type' => 'leaf',
'value_type' => 'uniline'
},
'GSSAPIDelegateCredentials',
{
'description' => 'Forward (delegate) credentials
to the server. The default is B<no>.Forward (delegate) credentials
to the server. The default is B<no>.',
'type' => 'leaf',
'upstream_default' => 'no',
'value_type' => 'boolean',
'write_as' => [
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Connector/Builtin/Authentication/LDAP.pm view on Meta::CPAN
$userdn = $dn;
last;
}
}
# restore the connection using the orginal credentials
$self->rebind();
if(!defined $userdn) {
$self->log()->warn('Authentication failed');
return 0;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Context/Singleton/Tutorial.pod view on Meta::CPAN
=head1 TASK
Let's have an application handling web requests and emails, eg ticket system.
Application has config file providing database credentials.
=head1 IMPLEMENTATION
=head2 Root context resources
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Control/CLI/Extreme.pm view on Meta::CPAN
($args{host}, $args{port}) = ($1, $2);
}
}
else {
my @validArgs = ('host', 'port', 'username', 'password', 'publickey', 'privatekey', 'passphrase',
'prompt_credentials', 'baudrate', 'parity', 'databits', 'stopbits', 'handshake',
'errmode', 'connection_timeout', 'timeout', 'read_attempts', 'wake_console',
'return_reference', 'blocking', 'data_with_error', 'terminal_type', 'window_size',
'callback', 'forcebaud', 'atomic_connect', 'non_recognized_login', 'generic_login');
%args = parseMethodArgs($pkgsub, \@_, \@validArgs);
}
view all matches for this distribution
view release on metacpan or search on metacpan
</termEntry>
<termEntry id="aid1602">
<descrip type="subjectField">5.2 Interpreting / interpretation</descrip>
<note>Rejected</note>
<langSet xml:lang="en" id="cid2088">
<descrip type="definition">[[interpreter]] who has qualifications or credentials for the specific job at hand and who exhibits interpreting skills, has experience and observes the code of ethics of the profession and is able to carry out an...
<admin type="source">ISO/AWI 188413.6</admin>
<descrip type="definition">Alt.def: </descrip>
<admin type="source"/>
<note/>
<note/>
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Coro/Amazon/SimpleDB.pm view on Meta::CPAN
=head1 ATTRIBUTES
=head2 aws_access_key
=head2 aws_secret_access_key
These are the AWS credentials providing access to your account. These
should be available on security credentials page of the AWS portal.
=head2 domain_name
A default domain to use for requests. This may be over-ridden in
requests passed as hash refs or objects.
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Couchbase/Client.pm view on Meta::CPAN
likely to know of alternate entry points, and thus the server list is only
useful for discovering the initial entry point.
=item username, password
Authentication credentials for the connection. Defaults to NULL
=item bucket
The bucket name for the connection. Defaults to C<default>
view all matches for this distribution
view release on metacpan or search on metacpan
eg/sendgrid view on Meta::CPAN
subject($subject),
plain_body($plain),
html_body($html),
);
# Sendgrid login credentials
my $username = 'yourlogin@sendgrid.net';
my $password = "yourpassword";
my $transport = Email::Sender::Transport::SMTP->new(
host => 'smtp.sendgrid.net',
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Crypt/Credentials.pm view on Meta::CPAN
use YAML::PP;
sub new {
my ($class, %args) = @_;
my $dir = rel2abs($args{dir} // catdir(curdir, 'credentials'));
my $check_file = catfile($dir, 'check.enc');
my $real_key;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Crypt/LE.pm view on Meta::CPAN
$self->{tos_changed} = 1;
$tos_message = "You need to accept TOS at $self->{links}->{'terms-of-service'}";
}
$self->_debug("New key is now registered, reg path: $self->{directory}->{reg}. $tos_message");
} elsif ($status == BAD_REQUEST and $kid and $mac and $self->_pull_error($content)=~/not awaiting/) {
# EAB credentials were already associated with the key.
if ($self->{directory}->{reg}) {
$self->_debug("EAB credentials already associated. Account URL is: $self->{directory}->{reg}.");
} else {
return $self->_status(ERROR, "EAB credentials already associated and no EAB id was provided.");
}
} else {
return $self->_status(ERROR, $content);
}
if ($self->{registration_info} and ref $self->{registration_info} eq 'HASH') {
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Crypt/OPAQUE.pm view on Meta::CPAN
our $VERSION = 0.012;
our @ISA = qw(Exporter);
our @EXPORT = qw/
create_cleartext_credentials
store
recover
create_registration_request
create_registration_response
finalize_registration_request
derive_random_pwd
create_credential_request
create_credential_response
recover_credentials
/;
our @EXPORT_OK = @EXPORT;
sub recover_credentials {
my (
$cred_request, $cred_response, $pwd, $c_id, $s_id, $Nseed, $group_name, $info, $DST, $hash_name, $expand_message_func,
$mac_func, $pwd_harden_func, $unpack_func
) = @_;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Crypt/OpenSSL/CA/AlphabetSoup.pod view on Meta::CPAN
=over
=item *
the set of the cryptographic credentials (key and CA certificate) that
the CA-as-a-computing-equipment needs to perform,
=item *
the whole security domain (more computers and programs) that it relies
view all matches for this distribution
view release on metacpan or search on metacpan
Use of the C<HTTPS_PROXY> environment variable in this way
is similar to C<LWP::UserAgent->env_proxy()> usage, but calling
that method will likely override or break the C<Crypt::SSLeay>
support, so do not mix the two.
Basic auth credentials to the proxy server can be provided
this way:
# proxy_basic_auth
$ENV{HTTPS_PROXY_USERNAME} = 'username';
$ENV{HTTPS_PROXY_PASSWORD} = 'password';
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Crypt/XkcdPassword/Words/EN.pm view on Meta::CPAN
elegant
elbow
customs
cuban
credibility
credentials
consistent
collapse
cloth
claws
cinderella
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Curio/Role/GitLab/API/v4.pm view on Meta::CPAN
);
}
The C<myapp_secret> call is expected to be the place where you use
whatever tool you use to hold your GitLab tokens and likely all
passwords and other credentials (secrets) that your application needs.
Some common tools that people use to manage their secrets are
Kubernetes' secrets objects, AWS's Secret Manager, HashiCorp's Vault,
or just an inescure configuration file; to name a few.
view all matches for this distribution
view release on metacpan or search on metacpan
Parameters are all passed as a hash or hash reference whose keys are described below:
I<Connection Parameters>
To establish a connection to a datastore, the caller must pass credentials. These may be passed either in URL syntax and/or as separate keys. Any information passed separately overrides the appropriate value in the URL. If no connection informatio...
=over
=item DBED
view all matches for this distribution