Result:
found more than 606 distributions - search limited to the first 2001 files matching your query
( run in 0.952 )
App-SD
view release on metacpan or search on metacpan
lib/App/SD/ForeignReplica.pm view on Meta::CPAN
$login_args{secret_prompt} = $args{secret_prompt}
if $args{secret_prompt};
# allow prompting for just password if username already specified
# and vice-versa for password
# if both are specified, we still want to loop in case the
# credentials are wrong
$login_args{username} = $args{username} if $args{username};
$login_args{password} = $args{password} if $args{password};
while (!$login_successful) {
( $username, $password ) = $self->prompt_for_login(%login_args);
App-SFDC
view release on metacpan or search on metacpan
lib/App/SFDC/Role/Credentials.pm view on Meta::CPAN
format => 'i',
default => 34;
option 'credfile',
doc => 'The file from which to read credentials.',
is => 'ro',
format => 's',
lazy => 1,
default => File::HomeDir->my_home."/.salesforce.properties",
isa => sub {
LOGDIE "The credentials file ".$_[0]." doesn't exist!"
unless -e $_[0];
};
option 'environment',
lib/App/SFDC/Role/Credentials.pm view on Meta::CPAN
Config::Properties
->new(file => $self->credfile)
->splitToTree()
};
LOGDIE "Couldn't find credentials for $environment in "
.$self->credfile
unless $environments{$environment};
for (qw'username password url apiversion'){
if (exists($environments{$environment}->{$_})){
lib/App/SFDC/Role/Credentials.pm view on Meta::CPAN
=head2 --credfile
A config file containing details of your enviroments, similar to the ant
deployment.properties file. For each environment, this file may specify the
credentials for that environment as:
envname.username = username@example.com
envname.password = PASSWORDthenTOKEN
envname.url = https://login.salesforce.com
App-Smbxfer
view release on metacpan or search on metacpan
lib/App/Smbxfer.pm view on Meta::CPAN
use Filesys::SmbClient;
# Exports...
use base qw( Exporter );
our @EXPORT_OK = qw(
credentials do_smb_transfer parse_smb_spec
create_smb_dir_path create_local_dir_path smb_element_type
smb_upload smb_download
);
__PACKAGE__->run unless caller;
lib/App/Smbxfer.pm view on Meta::CPAN
--usage|help
Command-line options:
--options
Name of file containing credentials (standard smb credentials file):
--cred <credentials-filename>
Transfer directory <local-name>:
--recursive
Create parent directories:
lib/App/Smbxfer.pm view on Meta::CPAN
die usage unless defined $source && defined $dest;
# Ensure that exactly one of source/dest is in "SMB path spec" format...
($dest =~ m|^//|) xor ($source =~ m|^//|) or die usage;
# Get access credentials for SMB connection...
my ($username, $password, $domain) = credentials($cred);
# Prepare SMB connection object...
my $smb = Filesys::SmbClient->new(
username => $username, password => $password, workgroup => $domain
);
lib/App/Smbxfer.pm view on Meta::CPAN
);
}
#########################
sub credentials {
my ($credentials_filename) = @_;
my ($username, $password, $domain);
if ($credentials_filename) {
# Read access credentials from file formatted using standard smbmount
# syntax...
open( my $credentials, '<', "$credentials_filename" )
or croak "cannot open credentials file: $!";
my @lines;
while( <$credentials> ){
my ($value) = (m/.*=\s+?(.*)$/);
push @lines, $value;
}
close $credentials;
($username, $password, $domain) = @lines;
}
else {
# Getting credentials interactively...
$username = prompt( "username? " );
$password = prompt( "password? ", -e => '*' );
$domain = prompt( "domain? " );
}
lib/App/Smbxfer.pm view on Meta::CPAN
=head2 run
"main() method" for running module as a command-line program.
=head2 credentials
my ($username, $password, $domain) = credentials( $credentials_file );
Load SMB access credentials from the specified filename, which should be
formatted as expected by the smb* suite of tools (smbclient, etc.)
=head2 validated_paths
my ($local_path, $remote_smb_path_spec) = validated_paths(
lib/App/Smbxfer.pm view on Meta::CPAN
--usage|help
Command-line options:
--options
Name of file containing credentials (standard smb credentials file):
--cred <credentials-filename>
Transfer directory <local-name>:
--recursive
Create parent directories:
lib/App/Smbxfer.pm view on Meta::CPAN
=head1 PROGRAM: OPTIONS
This program can be given an option, '--cred', that specifies the path to a
filename containing Samba access credentials, explained in the CONFIGURATION AND
ENVIRONMENT section.
For recursive transfers, the '--recursive' flag is supported. The '--parents'
flag causes the entire directory structure from the source path argument to be
replicated at the destination. If the source path argument is a relative path,
lib/App/Smbxfer.pm view on Meta::CPAN
Command-line options were not recognized. C<< --usage >> and C<< --options >> provide
succinct information to resolve.
=item C<< cannot open credentials file: ... >>
The specified Samba access credentials file could not be opened.
=item C<< Error: SMB specification F< smb path spec > not found >>
Could not connect to the indicated Samba server/share/path.
lib/App/Smbxfer.pm view on Meta::CPAN
=back
=head1 PROGRAM: CONFIGURATION AND ENVIRONMENT
The credentials file that can be used via the '--cred' option should be in the
same format used by smbclient. This file looks as follows:
username = <username>
password = <password>
domain = <domain>
App-SpamcupNG
view release on metacpan or search on metacpan
lib/App/SpamcupNG/Error/LoginFailed.pm view on Meta::CPAN
See L<App::SpamcupNG::Error::Factory> instead of creating it manually.
=head1 DESCRIPTION
A login failed means there is a problem with your Spamcop account credentials.
=head1 METHODS
=head2 new
App-Spoor
view release on metacpan or search on metacpan
lib/App/Spoor/ApiClient.pm view on Meta::CPAN
my $user_agent = shift;
my $config = shift;
my $uri = $config->{host} . '/api/reports?' . http_build_query({reports => {host => $host}});
my $credentials = 'Basic ' . encode_base64(
$config->{credentials}{api_identifier} . ':' . $config->{credentials}{api_secret}
);
my $response = $user_agent->get(
$uri,
'Authorization' => $credentials,
'HTTP-Accept' => 'application/json'
);
from_json($response->content)->{reports};
}
lib/App/Spoor/ApiClient.pm view on Meta::CPAN
my $user_agent = shift;
my $config = shift;
my $uri = $config->{host} . '/api/mailbox_events?' . http_build_query({mailbox_events => {host => $host}});
my $credentials = 'Basic ' . encode_base64(
$config->{credentials}{api_identifier} . ':' . $config->{credentials}{api_secret}
);
my $response = $user_agent->get(
$uri,
'Authorization' => $credentials,
'HTTP-Accept' => 'application/json'
);
from_json($response->content)->{mailbox_events};
}
App-SpreadRevolutionaryDate
view release on metacpan or search on metacpan
- Update autogenerated git readme
- Add localization for spread message, only fr (default) or en!
- Use config objects to test targets, using directly targets may lead to
undef
- Add SEE ALSO section in all modules pods
- Fix nb tests in freenode_fake_credentials to pass Test::NoWarnings
0.05 2019-03-07T08:01:25Z
- Move test no authentication to Freenode with fake credentials in xt
- Fix escaping of greater than sign in pod formatting code
- Use warnings in App::SpreadRevolutionaryDate::Config
0.04 2019-03-06T22:24:19Z
- Add clean-namespace and unused-vars tests in MANIFEST
testing multiple Freenode bots
- Add documentation about optional argument to
App::SpreadRevolutionaryDate constructor
- Add tests for spreading to Mastodon
- Add tests for spreading to Twitter
- Test authentication to Freenode with actual credentials in user config
- Test no authentication on Freenode with fake credentials
- Test no authentication on Mastodon with fake credentials
- Move authentication to Freenode to spread method
- Move subclass of Bot::BasicBot outside of
App::SpreadRevolutionaryDate::Freenode
- Disable coerce_entities since Mastodon::Client has trouble coercing
Account
- Fix Bot::BasicBot methods calls
- Add abstract for subclasses
- Test Freenode configuration options
- Test Mastodon configuration options
- Test setting explicit target as command line argument
- Rename authentication test with actual credentials in user config
- Test authentication to Mastodon with actual credentials in user config
- Test setting option as command line argument
- Add pod documentation for methods
- Disable pod coverage tests for now
- Add tests for spreading objects with actual credentials in user config
- Test no authentication on Twitter with fake credentials
- Add fake configuration for tests
- Rename test file
- Switch to ExtUtils::MakeMaker instead of Module::Build::Tiny
- Add no warnings test for spreading objects
- Add tests for spreading objects
App-Sqitch
view release on metacpan or search on metacpan
lib/App/Sqitch/Engine/clickhouse.pm view on Meta::CPAN
return $val eq 'true' || $val eq 'yes' || $val eq 'on' || 0;
}
# Connection name defaults to host name from url, or else hostname from config
# or else localhost. Then look for that name in a connection under
# `connections_credentials`. If it exists, copy/overwrite `hostname`, `port`,
# `secure`, `user`, `password`, and `database`. Fall back on root object
# values `host` (not `hostname`) `port`, `secure`, `user`, `password`, and
# `database`.
#
# https://github.com/ClickHouse/ClickHouse/blob/d0facf0/programs/client/Client.cpp#L139-L212
lib/App/Sqitch/Engine/clickhouse.pm view on Meta::CPAN
# Copy client TLS config if exists.
if (my $tls = $cfg->{openSSL}) {
$conn->{tls} = $tls->{client} if $tls->{client};
}
# Copy connection credentials for this host if they exists.
$host ||= $cfg->{host} || 'localhost';
my $creds = $cfg->{connections_credentials} or return $conn;
my $conns = $creds->{connection} or return $conn;
for my $c (@{ ref $conns eq 'ARRAY' ? $conns : [$conns] }) {
next unless ($c->{name} || '') eq $host;
if (exists $c->{secure}) {
$conn->{secure} = _is_true $c->{secure}
App-TimeTracker-Command-Jira
view release on metacpan or search on metacpan
lib/App/TimeTracker/Command/Jira.pm view on Meta::CPAN
Username to connect with.
=head3 password [OPTIONAL]
Password to connect with. Beware: This is stored in clear text! Better use authentication via C<Config::Identity> via C<JIRA::REST> where the credentials can be stored GPG encrypted.
=head3 token [OPTIONAL]
Token to authenticate with. Can be generated in Jira user profile.
See L<https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html>
App-Toot
view release on metacpan or search on metacpan
lib/App/Toot/Config.pm view on Meta::CPAN
Returns a hashref of the loaded config for the defined section name.
=head1 CONFIGURATION
To post to Mastodon, you need to provide the account's oauth credentials in the file C<config.ini>.
An example is provided as part of this distribution. The user running the L<toot> script, for example through cron, will need access to the configuration file.
To set up the configuration file, copy C<config.ini.example> into one of the following locations:
lib/App/Toot/Config.pm view on Meta::CPAN
=item C</etc/toot/config.ini>
=back
After creating the file, edit and update the values in the C<default> section to match the account's oauth credentials.
[default]
instance = mastodon.social
username = youruser
client_id = OKE98_kdno_NOTAREALCLIENTID
App-TypecastTemplates
view release on metacpan or search on metacpan
lib/App/TypecastTemplates.pm view on Meta::CPAN
if (!keys %$templates) {
read_templates(\*DATA);
}
}
open(my $handle, '<' . $fn)
or die "can't open credentials file '$fn'";
if ($columns) {
$csv->column_names( split(/,/,$columns) );
}
else {
my @cols = $csv->getline( $handle );
App-Validation-Automation
view release on metacpan or search on metacpan
lib/App/Validation/Automation/Web.pm view on Meta::CPAN
Stores utilities that perform web based validation
=head1 SYNOPSIS
App::Validation::Automation::Web browses the web urls stored in config or passed as arguments using WWW::Mechanize Logs into the web urls using the credentials stored in attributes.Handles password expiry and authentication failure along with DNS rou...
=head1 ATTRIBUTES
user_name houses the login name needed to login into the web url.password stores the decrypted password.
App-WatchLater
view release on metacpan or search on metacpan
lib/App/WatchLater/YouTube.pm view on Meta::CPAN
=head1 SYNOPSIS
This is a simple module for making requests to the YouTube Data API.
Authorization is required, and can be obtained by registering for an API key
from the Google Developer L<API
Console|https://console.developers.google.com/apis/credentials>. Alternatively,
obtain user authorization through OAuth2 using the yt-oauth(1) script.
my $api = App::WatchLater::YouTube->new(
access_token => ...,
api_key => ...,
App-WordPressTools
view release on metacpan or search on metacpan
script/wp-tools view on Meta::CPAN
$database =~ s/^[\r\n]+//;
chomp $username;
chomp $password;
chomp $database;
if ($username =~ /[\r\n]/ || $password =~ /[\r\n]/ || $database =~ /[\r\n]/) {
die "Multiple credentials found in $args->{'path'}/wp-config.php. Cannot determine which to use. Backup operation halted.";
}
open (my $fh, '>', $defaults_file) or die "Cannot write to $defaults_file: $!";
close $fh;
chmod(0600, $defaults_file) or die "Cannot chmod $defaults_file: $!";
write_text($defaults_file,"[client]\nuser=$username\npassword=$password");
script/wp-tools view on Meta::CPAN
$database =~ s/^[\r\n]+//;
chomp $username;
chomp $password;
chomp $database;
if ($username =~ /[\r\n]/ || $password =~ /[\r\n]/ || $database =~ /[\r\n]/) {
die "Multiple credentials found in $args->{'path'}/wp-config.php. Cannot determine which to use. Restoration operation halted.";
}
open (my $fh, '>', $defaults_file) or die "Cannot write to $defaults_file: $!";
close $fh;
chmod(0600, $defaults_file) or die "Cannot chmod $defaults_file: $!";
write_text($defaults_file,"[client]\nuser=$username\npassword=$password");
script/wp-tools view on Meta::CPAN
$database =~ s/^[\r\n]+//;
chomp $username;
chomp $password;
chomp $database;
if ($username =~ /[\r\n]/ || $password =~ /[\r\n]/ || $database =~ /[\r\n]/) {
die "Multiple credentials found in $args->{'path'}/wp-config.php. Cannot determine which to use. Upgrade operation halted.";
}
if ($prefix =~ /[\r\n]/) {
die "Multiple database prefixes found in $args->{'path'}/wp-config.php. Cannot determine which to use. Upgrade operation halted.";
}
open (my $fh, '>', $defaults_file) or die "Cannot write to $defaults_file: $!";
App-ZofCMS
view release on metacpan or search on metacpan
lib/App/ZofCMS/Plugin/UserLogin.pm view on Meta::CPAN
B<Optional>. Takes a scalar as a value that represents a query parameter
name into which to store the URI of the page that not-logged-in user
attempted to access. This option works only when C<redirect_on_login> is
specified. When specified, plugin enables the magic to "remember" the page
that a not-logged-in user tried to access, and once the user enters correct
login credentials, he is redirected to said page automatically; thereby
making the login process transparent. B<By default> is not specified.
=head2 C<preserve_login>
preserve_login => 'my_site_login',
App-coinbasepro-lite
view release on metacpan or search on metacpan
lib/App/coinbasepro/lite.pm view on Meta::CPAN
schema => 'str*',
default => 'GET',
},
);
my %args_credentials = (
key => {
schema => ['str*'],
req => 1,
},
secret => {
lib/App/coinbasepro/lite.pm view on Meta::CPAN
$SPEC{private} = {
v => 1.1,
summary => 'Perform a public API request',
args => {
%args_credentials,
%args_common,
},
};
sub private {
my %args = @_;
App-cryp-exchange
view release on metacpan or search on metacpan
lib/App/cryp/Role/Exchange.pm view on Meta::CPAN
You have to specify one of base_size or quote_size, but not both.
=back
Some specific exchanges might require more credentials or arguments (e.g.
C<api_passphrase> on Coinbase Pro); please check with the specific drivers.
When successful, payload in response must be a hashref which contains at least
these keys: C<type> ("buy" or "sell"), C<pair>, C<order_id> (str, usually a
number, can also be a UUID, etc), C<price> (number, actual price of the order),
lib/App/cryp/Role/Exchange.pm view on Meta::CPAN
String. Required.
=back
Some specific exchanges might require more credentials or arguments (e.g.
C<api_passphrase> on GDAX); please check with the specific drivers.
Method must return object.
=head1 HOMEPAGE
App-gcal
view release on metacpan or search on metacpan
lib/App/gcal.pm view on Meta::CPAN
require Net::Netrc;
my $netrc = Net::Netrc->lookup('google.com');
unless ($netrc) {
die(
'Error. Could not find your credentials in your .netrc file'
);
}
$username = $netrc->login;
$password = $netrc->password;
lib/App/gcal.pm view on Meta::CPAN
=head1 DESCRIPTION
The C<gcal> command provides a quick and easy interface to Google Calendar from the command line.
Before using the C<gcal> command, you need to provide your Google credentials. The most convenient way to do this is by using your C<~.netrc> file and supplying credentials for the C<google.com> machine. For example:
machine google.com
login bill
password 1234
App-gh
view release on metacpan or search on metacpan
lib/App/gh/Command/Fork.pm view on Meta::CPAN
my $gh_id = App::gh->config->github_id;
my $gh_token = App::gh->config->github_token
|| App::gh->config->github_password;
unless( $gh_id && $gh_token ) {
die "Github credentials not found. Cannot fork repository.\n";
}
unless ( $repo ) {
# detect .git directory
App-gist
view release on metacpan or search on metacpan
lib/App/gist.pm view on Meta::CPAN
around _request_for => sub {
my ($orig, $self, @args) = @_;
my $req = $self -> $orig(@args);
my ($login, $passwd) = App::gist::_get_credentials();
$req -> headers -> remove_header('Authorization');
$req -> headers -> authorization_basic($login, $passwd);
return $req;
lib/App/gist.pm view on Meta::CPAN
}
}
);
}
sub _get_credentials {
my ($login, $pass, $token);
my %identity = Config::Identity::GitHub -> load
if try_load_class('Config::Identity::GitHub');
App-git-ship
view release on metacpan or search on metacpan
lib/App/git/ship.pm view on Meta::CPAN
The main focus is to automate away the boring steps, but at the same time not
get in your (or any random contributor's) way. Problems should be solved with
sane defaults according to standard rules instead of enforcing more rules.
L<App::git::ship> differs from other tools like L<dzil|Dist::Zilla> by I<NOT>
requiring any configuration except for a file containing the credentials for
uploading to CPAN.
=head2 Supported project types
Currently, only L<App::git::ship::perl> is supported.
App-git_log_ch_usrdata
view release on metacpan or search on metacpan
script/git_log_ch_usrdata view on Meta::CPAN
my ($Old_Mail, $New_Mail, $New_User, $No_Credentials);
GetOptions('old_email|oe=s' => \$Old_Mail,
'new_email|ne=s' => \$New_Mail,
'new_user|nu=s' => \$New_User,
'no_credentials|nc' => \$No_Credentials
) or pod2usage(2);
$Old_Mail // die("'--old_email' missing.");
$New_Mail // die("'--new_email' missing.");
$New_User // die("'--new_user' missing.");
script/git_log_ch_usrdata view on Meta::CPAN
'git gc --prune=now --aggressive',
'echo "--- push changes to github ---"',
"git push --force --tags origin 'refs/heads/*'",
$No_Credentials ? () : (
'echo "--- Set credentials ---"',
'git config credential.helper store',
"git config user.email $New_Mail",
"git config user.name \$New_User"
)
);
script/git_log_ch_usrdata view on Meta::CPAN
=head1 SYNOPSIS
git_log_ch_usrdata --old_email OLD_EMAIL --new_email NEW_EMAIL \
--new_user NEW_USER [--no_credentials]
git_log_ch_usrdata --help | --version
or, shorter:
script/git_log_ch_usrdata view on Meta::CPAN
git_log_ch_usrdata --oe OLD_EMAIL --ne NEW_EMAIL --nu NEW_USER
By default, the script also stores I<C<NEW_EMAIL>> and I<C<NEW_USER>> via
C<git config credential.helper store>. This can be switched off by specifying
the B<C<--no_credentials>> (or B<C<--nc>>) option.
=head1 SEE ALSO
L<App::ghmulti>, L<App::git_log_ch_usrdata>
App-html2wp
view release on metacpan or search on metacpan
lib/App/html2wp.pm view on Meta::CPAN
v => 1.1,
summary => 'Publish HTML document to WordPress as blog post',
description => <<'_',
To use this program, first create `~/html2wp.conf` containing the API
credentials, e.g.:
proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
password=YOURPASSWORD
You can also put multiple credentials in the configuration file using profile
sections, e.g.:
[profile=blog1]
proxy=https://YOURBLOG1NAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
lib/App/html2wp.pm view on Meta::CPAN
html2wp(%args) -> [status, msg, payload, meta]
Publish HTML document to WordPress as blog post.
To use this program, first create C<~/html2wp.conf> containing the API
credentials, e.g.:
proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
password=YOURPASSWORD
You can also put multiple credentials in the configuration file using profile
sections, e.g.:
[profile=blog1]
proxy=https://YOURBLOG1NAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
App-karr
view release on metacpan or search on metacpan
/cover_db/
/blib/
/pm_to_blib
# Claude Code - commit: skills/, agents/, hooks/, settings.json
# Ignore: local overrides, credentials, session data
!/.claude/
.claude/*
!.claude/settings.json
!.claude/agents/
!.claude/agents/**
!.claude/skills/**
!.claude/hooks/
!.claude/hooks/**
.claude/*.local.*
.claude/local/
.claude/.credentials.json
.claude/statsig/
.claude/todos/
.claude/projects/
AGENTS.md
App-org2wp
view release on metacpan or search on metacpan
lib/App/org2wp.pm view on Meta::CPAN
This is originally a quick hack because I couldn't make
[org2blog](https://github.com/punchagan/org2blog) on my Emacs installation to
work after some update. `org2wp` uses the same format as `org2blog`, but instead
of being an Emacs package, it is a CLI script written in Perl.
First, create `~/org2wp.conf` containing the API credentials, e.g.:
; use INI (IOD) format for this file
proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
password=YOURPASSWORD
lib/App/org2wp.pm view on Meta::CPAN
server, which can be hosted on `wordpress.com` or on other server, including
your own. It has nothing to do with HTTP/HTTPS proxy; the term "proxy" is used
by the <pm:XMLRPC::Lite> and <pm:SOAP::Lite> Perl libraries and `org2wp` simply
uses the same terminology.
You can also put multiple credentials in the configuration file using profile
sections, e.g.:
; use INI (IOD) format for this file
[profile=blog1]
proxy=https://YOURBLOG1NAME.wordpress.com/xmlrpc.php
lib/App/org2wp.pm view on Meta::CPAN
This is originally a quick hack because I couldn't make
LL<https://github.com/punchagan/org2blog> on my Emacs installation to
work after some update. C<org2wp> uses the same format as C<org2blog>, but instead
of being an Emacs package, it is a CLI script written in Perl.
First, create C<~/org2wp.conf> containing the API credentials, e.g.:
; use INI (IOD) format for this file
proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
password=YOURPASSWORD
lib/App/org2wp.pm view on Meta::CPAN
server, which can be hosted on C<wordpress.com> or on other server, including
your own. It has nothing to do with HTTP/HTTPS proxy; the term "proxy" is used
by the L<XMLRPC::Lite> and L<SOAP::Lite> Perl libraries and C<org2wp> simply
uses the same terminology.
You can also put multiple credentials in the configuration file using profile
sections, e.g.:
; use INI (IOD) format for this file
[profile=blog1]
proxy=https://YOURBLOG1NAME.wordpress.com/xmlrpc.php
App-pepper
view release on metacpan or search on metacpan
lib/App/pepper.pm view on Meta::CPAN
my $handlers = {
'timeout' => \&handle_timeout,
'ssl' => \&handle_ssl,
'host' => \&handle_host,
'port' => \&handle_port,
'credentials' => \&handle_credentials,
'id' => \&handle_id,
'pw' => \&handle_pw,
'newpw' => \&handle_newpw,
'connect' => \&handle_connect,
'login' => \&handle_login,
lib/App/pepper.pm view on Meta::CPAN
}
return $result;
}
}
sub handle_credentials {
if ($_[0] eq '') {
return error('Missing client ID');
} elsif ($_[1] eq '') {
return error('Missing password');
lib/App/pepper.pm view on Meta::CPAN
} elsif ($epp->{'host'} eq '') {
return error('No host specified');
} elsif ($epp->{'user'} eq '' || $epp->{'pass'} eq '') {
return error('No credentials specified');
} else {
note("Attempting to login as '%s'...", $epp->{'user'});
$epp->{'quiet'} = ($verbose ? 0 : 1);
my $result = $epp->_login;
lib/App/pepper.pm view on Meta::CPAN
my %map = (
'timeout' => 'SYNTAX/Connection Management',
'ssl' => 'SYNTAX/Connection Management',
'host' => 'SYNTAX/Connection Management',
'port' => 'SYNTAX/Connection Management',
'credentials' => 'SYNTAX/Session Management',
'id' => 'SYNTAX/Session Management',
'pw' => 'SYNTAX/Session Management',
'newpw' => 'SYNTAX/Session Management',
'connect' => 'SYNTAX/Connection Management',
'login' => 'SYNTAX/Session Management',
App-perldebs
view release on metacpan or search on metacpan
t/features/step_definitions/basic.pl~ view on Meta::CPAN
use warnings;
use lib 't/lib';
use Test::Helper qw(testmojo create_user testschema);
use Test::StepsHelper
qw(a_login_request_with_invalid_credentials get_result api_base );
use Test::Net::LDAP::Util qw(ldap_mockify);
use Test::More;
use Test::BDD::Cucumber::StepFile;
t/features/step_definitions/basic.pl~ view on Meta::CPAN
create_user( context => $context );
};
};
When qr{the client tries to login without providing a user name} => sub {
my $request = a_login_request_with_invalid_credentials();
delete $request->{username};
$t->post_ok( $route => $accept_header => json => $request );
};
When qr{the client tries to login without providing a password} => sub {
my $request = a_login_request_with_invalid_credentials();
delete $request->{password};
$t->post_ok( $route => $accept_header => json => $request );
};
When
qr{the client tries to log in providing correct password for this existing user}
=> sub {
my $request = a_login_request_with_invalid_credentials();
$request->{username} = C->stash->{scenario}->{username};
$request->{password} = C->stash->{scenario}->{password};
# deep within this login there's a bind() which we have to mock
ldap_mockify {
$t->post_ok( $route => $accept_header => json => $request );
}
};
When qr{the client tries to login providing name of non-existing user} => sub {
my $request = a_login_request_with_invalid_credentials();
$request->{username} = 'I do not exist';
$t->post_ok( $route => $accept_header => json => $request );
};
When
App-pod2wp
view release on metacpan or search on metacpan
lib/App/pod2wp.pm view on Meta::CPAN
This is like <prog:org2wp> except that instead of Org as the document format,
this program uses POD.
To use this program, first create `~/pod2wp.conf` containing the API
credentials, e.g.:
proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
password=YOURPASSWORD
You can also put multiple credentials in the configuration file using profile
sections, e.g.:
[profile=blog1]
proxy=https://YOURBLOG1NAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
lib/App/pod2wp.pm view on Meta::CPAN
This is like L<org2wp> except that instead of Org as the document format,
this program uses POD.
To use this program, first create C<~/pod2wp.conf> containing the API
credentials, e.g.:
proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
password=YOURPASSWORD
You can also put multiple credentials in the configuration file using profile
sections, e.g.:
[profile=blog1]
proxy=https://YOURBLOG1NAME.wordpress.com/xmlrpc.php
username=YOURUSERNAME
App-rdapper
view release on metacpan or search on metacpan
lib/App/rdapper.pm view on Meta::CPAN
=item * C<--short> - omit remarks, notices, links and redactions.
=item * C<--bypass-cache> - disable local cache of RDAP objects.
=item * C<--auth=USER:PASS> - HTTP Basic Authentication credentials to be used
when accessing the specified resource. This option B<SHOULD NOT> be used unless
you explicitly specify a URL, otherwise your credentials may be sent to servers
you aren't expecting them to.
=item * C<--nocolor> - disable ANSI colors in the formatted output.
=item * C<--debug> -run in debugging mode.
App-sdseasydyn
view release on metacpan or search on metacpan
## Features
- Simple CLI interface (`sdseasydyn update`)
- Clear configuration precedence: CLI > environment > config file > defaults
- Secure handling of credentials (tokens are never logged)
- Public IPv4 discovery with configurable endpoint
- Local state file to avoid redundant updates
- Bounded retry logic using `Retry::Policy`
- Suitable for unattended / scheduled execution
( run in 0.952 second using v1.01-cache-2.11-cpan-39bf76dae61 )