view release on metacpan or  search on metacpan

lib/App/MFILE/WWW/Dispatch.pm  view on Meta::CPAN

    # POST is used only for login/logout ATM
    if ( $method =~ m/^LOGIN/i ) {
        $log->debug( "Incoming login/logout attempt" );
        if ( $path =~ m/^login/i ) {
            return $self->validate_user_credentials( $body );
        } else {
            return $self->_logout( $body );
        }
    }

    $log->crit( "Asked to perform an AJAX call, but feature is not implemented!" );
    return 0;
}


=head2 validate_user_credentials

Called from C<process_post> to process login requests (special AJAX requests)
originating from the JavaScript side (i.e. the login screen in
login-dialog.js, via login.js).

Returns a status object - OK means the login was successful; all other statuses
mean unsuccessful.

=cut

sub validate_user_credentials {
    my ( $self, $body ) = @_;
    $log->debug( "Entering " . __PACKAGE__ . "::validate_user_credentials()" );

    my $r = $self->request;
    my $session = $r->{'env'}->{'psgix.session'};
    my $nick = $body->{'nam'};
    my $password = $body->{'pwd'};

 view release on metacpan or  search on metacpan

lib/App/MFILE/HTTP.pm  view on Meta::CPAN

    }

    # login bypass
    $meta->set('META_LOGIN_BYPASS_STATE', 0) if not defined $meta->META_LOGIN_BYPASS_STATE;
    if ( $site->MFILE_WWW_BYPASS_LOGIN_DIALOG and not $meta->META_LOGIN_BYPASS_STATE ) {
        $log->notice("Bypassing login dialog! Using default credentials");
        $session->{'ip_addr'} = $remote_addr;
        $session->{'last_seen'} = time;
        my $bypass_result = $self->_login_dialog( {
            'nam' => $site->MFILE_WWW_DEFAULT_LOGIN_CREDENTIALS->{'nam'},
            'pwd' => $site->MFILE_WWW_DEFAULT_LOGIN_CREDENTIALS->{'pwd'},

 view release on metacpan or  search on metacpan

share/public_html/static/music_inc/drflac.js  view on Meta::CPAN

  
  return (
function(Module) {
  Module = Module || {};

var Module=typeof Module!="undefined"?Module:{};var readyPromiseResolve,readyPromiseReject;Module["ready"]=new Promise(function(resolve,reject){readyPromiseResolve=resolve;readyPromiseReject=reject});["_network_drflac_open_mem","_network_drflac_read_...


  return Module.ready
}
);

 view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

0.026
          - Add --trial option to regenerate/upload/dist/distdir

0.025     Sun Dec 16 22:09:12 CET 2018
          - Allow fetching credentials from console
          - Add SPDX support to meta files

0.024
          - Write generated files as binary
          - Decode author names when POD is encoded

 view release on metacpan or  search on metacpan

lib/App/MtAws/GlacierRequest.pm  view on Meta::CPAN

	my $canonical_url_hash = sha256_hex($canonical_url);


	# /getting canonical URL

	my $credentials = "$datestr/$self->{region}/$self->{service}/aws4_request";

	my $string_to_sign = join("\n", "AWS4-HMAC-SHA256", $date8601, $credentials, $canonical_url_hash);

	my ($kSigning, $kSigning_hex) = get_signature_key($self->{secret}, $datestr, $self->{region}, $self->{service});
	my $signature = hmac_sha256_hex($string_to_sign, $kSigning);



	my $auth = "AWS4-HMAC-SHA256 Credential=$self->{key}/$credentials, SignedHeaders=$signed_headers, Signature=$signature";

	push @{$self->{req_headers}}, { name => 'Authorization', value => $auth};
}

 view release on metacpan or  search on metacpan

public/javascripts/ace/mode-redshift.js  view on Meta::CPAN

var JsonHighlightRules = require("./json_highlight_rules").JsonHighlightRules;

var RedshiftHighlightRules = function() {
    var keywords = (
        "aes128|aes256|all|allowoverwrite|analyse|analyze|and|any|array|as|asc|authorization|backup|" + 
        "between|binary|blanksasnull|both|bytedict|bzip2|case|cast|check|collate|column|constraint|create|credentials|" + 
        "cross|current_date|current_time|current_timestamp|current_user|current_user_id|default|deferrable|deflate|defrag|delta|" + 
        "delta32k|desc|disable|distinct|do|else|emptyasnull|enable|encode|encrypt|encryption|end|except|explicit|false|for|foreign|" + 
        "freeze|from|full|globaldict256|globaldict64k|grant|group|gzip|having|identity|ignore|ilike|in|initially|inner|intersect|into|is|" + 
        "isnull|join|leading|left|like|limit|localtime|localtimestamp|lun|luns|lzo|lzop|minus|mostly13|mostly32|mostly8|natural|new|not|notnull|" + 
        "null|nulls|off|offline|offset|old|on|only|open|or|order|outer|overlaps|parallel|partition|percent|permissions|placing|primary|raw|readratio|" +

 view release on metacpan or  search on metacpan

lib/App/Netdisco/Util/DeviceAuth.pm  view on Meta::CPAN

use Try::Tiny;

use base 'Exporter';
our @EXPORT = ();
our @EXPORT_OK = qw/
  fixup_device_auth get_external_credentials
/;
our %EXPORT_TAGS = (all => \@EXPORT_OK);

=head1 NAME

 view release on metacpan or  search on metacpan

share/mib/lldp.mib  view on Meta::CPAN

    DESCRIPTION
            "The value of a management address associated with the LLDP
            agent that may be used to reach higher layer entities to
            assist discovery by network management.

            It should be noted that appropriate security credentials,
            such as SNMP engineId, may be required to access the LLDP
            agent using a management address.  These necessary credentials
            should be known by the network management and the objects
            associated with the credentials are not included in the
            LLDP agent."
    SYNTAX      OCTET STRING (SIZE (1..31))

LldpSystemCapabilitiesMap ::= TEXTUAL-CONVENTION
    STATUS      current

 view release on metacpan or  search on metacpan

lib/App/Nopaste/Service/Dancebin.pm  view on Meta::CPAN

sub uri { $ENV{DANCEBIN_URL} || 'http://danceb.in/' }

sub get {
    my ($self, $mech) = @_;

    # Set BasicAuth credentials if needed
    $mech->credentials( $self->_credentials ) if $self->_credentials;

    return $mech->get($self->uri);
}

sub fill_form {

 view release on metacpan or  search on metacpan

lib/App/OTRS/CreateTicket.pm  view on Meta::CPAN

=head1 DESCRIPTION

This module contains one script, L<otrs.CreateTicket.pl>, which allows you to create
tickets in OTRS from the command line.

For creating a ticket you'll need to have valid OTRS agent login credentials, as well
as the TicketConnector web service installed on your OTRS machine. In order to use the
GenericTicketConnector you need to use at least OTRS 3.1.

Activating the TicketConnector is easy. Download the yml file from the following URL:
L<https://raw.github.com/mbeijen/App-OTRS-CreateTicket/master/examples/GenericTicketConnector.yml>

 view release on metacpan or  search on metacpan

MANIFEST  view on Meta::CPAN

lib/App/Oozie/Deploy/Validate/Spec/Coordinator.pm
lib/App/Oozie/Deploy/Validate/Spec/Workflow.pm
lib/App/Oozie/Deploy/ttlib/common.properties
lib/App/Oozie/Deploy/ttlib/coordinator_config_xml
lib/App/Oozie/Deploy/ttlib/ttree.cfg
lib/App/Oozie/Deploy/ttlib/workflow_credentials
lib/App/Oozie/Deploy/ttlib/workflow_global_xml_end
lib/App/Oozie/Deploy/ttlib/workflow_global_xml_start
lib/App/Oozie/Deploy/ttlib/workflow_parameters_xml_end
lib/App/Oozie/Deploy/ttlib/workflow_parameters_xml_start
lib/App/Oozie/Deploy/ttlib/workflow_sla_xml

 view release on metacpan or  search on metacpan

lib/App/PAIA/Command.pm  view on Meta::CPAN

        $self->logger->("deleted session file");
    }

    my $auth = $self->auth or $self->usage_error("missing PAIA auth server URL");

    # take credentials from command line or config file only
    my %params = (
        username   => $self->username,
        password   => $self->password,
        grant_type => 'password',
    );

 view release on metacpan or  search on metacpan

lib/App/PAUSE/Comaint.pm  view on Meta::CPAN

    $self->login_pause;
    $self->make_comaint($comaint, \@packages);
}

sub get_credentials {
    my $self = shift;

    my %rc;
    my $file = "$ENV{HOME}/.pause";
    if (eval { require Config::Identity }) {

 view release on metacpan or  search on metacpan

lib/App/PM/Website/Command/Install.pm  view on Meta::CPAN

        else
        {
            warn "Old version of LWP::UserAgent doesn't support ssl_opts"
        }
    }
    my %webdav_credentials = (
        -user  => $opt->{username},
        -pass  => $opt->{password},
        -url   => $opt->{url},
        -realm => "groups.perl.org",
    );
    print Dumper { credentials => \%webdav_credentials };
    $webdav->credentials(%webdav_credentials);
    $webdav->open( -url => $opt->{url} )
        or die sprintf( "failed to open url [%s] : %s\n",
        $opt->{url}, $webdav->message() );

    my %put_options = (

 view release on metacpan or  search on metacpan

t/WebDAV.t  view on Meta::CPAN

$item = first { $_->get_uri->path eq "/raw/" } @list;
ok($item && $item->is_collection, "Found /raw");
$item = first { $_->get_uri->path eq "/file/" } @list;
ok($item && $item->is_collection, "Found /files");

# Attempt to write a file without credentials
my $str = "Ganymede\n";
ok(not($dav->put(-local=>\$str, -url=>"https://$host:$port/raw/M%C3%B6%C3%B6n")),
   "Failed to post without token");

# Retry with credentials
$dav->credentials(-user => "alex", -pass => "hello", -realm => "Phoebe");
ok($dav->put(-local=>\$str, -url=>"https://$host:$port/raw/M%C3%B6%C3%B6n"),
   "Post gemtext with token");

# /raw
$resource = $dav->propfind(-url=>"/raw", -depth=>1);

 view release on metacpan or  search on metacpan

t/04-functional.t  view on Meta::CPAN

	plan tests => 5;
} else {
	plan skip_all => 'These tests require Travis CI';
}

# Local test database credentials
my $host = 'localhost';
my $schema = 'photodb';
my $user = 'photodb';
my $pass = 'photodb';

 view release on metacpan or  search on metacpan

t/files/moby11.txt  view on Meta::CPAN

*I am aware that down to the present time, the fish styled

Lamatins and Dugongs (Pig-fish and Sow-fish of the Coffins

of Nantucket) are included by many naturalists among the whales.

But as these pig-fish are a noisy, contemptible set,

mostly lurking in the mouths of rivers, and feeding on wet hay,

and especially as they do not spout, I deny their credentials

as whales; and have presented them with their passports to quit

the Kingdom of Cetology.





First:  According to magnitude I divide the whales into three primary BOOKS

 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);

 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',

 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;

 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

 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};
}

 view release on metacpan or  search on metacpan

lib/sqitch-authentication.pod  view on Meta::CPAN

=encoding UTF-8

=head1 Name

sqitch-authentication - Guide to using database authentication credentials with Sqitch

=head1 Description

For database engines that require authentication, Sqitch supports a number
of credential-specification options, and searches for them in a specific

 view release on metacpan or  search on metacpan

foo.db matches  view on Meta::CPAN

  EXAHOST = localhost:8563
  EXAUID = sys
  EXAPWD = exasol
  AUTHMETHOD = refreshtoken

When combining the above, Sqitch doesn't need to know any credentials; they are
stored somewhat safely in F<~/.exasol/profiles.xml> and F<~/.odbc.ini>:

  > sqitch status db:exasol:flipr_test
  # On database db:exasol:flipr_test
  # Project:  flipr

 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 log_time_spent

If set, an entry will be created in the ticket's work log