view release on metacpan or search on metacpan
lib/DBIx/DataStore.pm view on Meta::CPAN
my $db = DBIx::DataStore->new({ config => $config });
=head2 Configuring Database Passwords
Because DBIx::DataStore uses the normal DBI/DBD layers underneath, all the
usual methods of locating and presenting database credentials to the
appropriate database server are available. This includes methods such as the
C<.pgpass> file for PostgreSQL and equivalents for other RDBMSes. If your
DBIx::DataStore configuration does not include a C<pass> attribute for a given
database host, these alternate methods will be used as long as they are
properly configured.
view release on metacpan or search on metacpan
* Mon May 21 11:38:02 2007 CEST
DBIx::Easy v0.17 released
* Fri May 18 17:27:15 2007 CEST
(Easy.pm): MySQL 5 has a different message for bad credentials
commit only if AutoCommit is turned off to avoid spurious warnings
* Fri May 18 00:17:37 2007 CEST
(Easy.pm): fixed now method for Postgresql
view release on metacpan or search on metacpan
lib/DBIx/HTML.pm view on Meta::CPAN
=head1 SYNOPSIS
use DBIx::HTML;
my $generator = DBIx::HTML->connect( @db_credentials );
$generator->do( $query );
# supports multiple orientations
print $generator->portrait;
print $generator->landscape;
# stackable method calls:
print DBIx::HTML
->connect( @db_credentials )
->do( 'select foo,baz from bar' )
->landscape
;
# rotating attributes:
lib/DBIx/HTML.pm view on Meta::CPAN
=head1 METHODS
=over 4
=item C<connect( @database_credentials )>
Connects to the database. See L<DBI> for how to do that.
Optionally, create your own database handle and pass it:
my $dbh = DBI->connect ( @db_creds );
view release on metacpan or search on metacpan
lib/DBIx/JCL.pm view on Meta::CPAN
the various execution and output parsing that whould otherwise have to be \
handled by calling the db_sqlloader functions directly (which certainly you \
can if you prefer).
Execute SQL*Loader using the supplied paramaters. The Virtual Database \
Name is used to obtain login credentials. This will launch SQL*Loader \
and wait for it to finish, returning the SQL*Loader return code to the \
caller.
Data file name must be fully qualified. Path provided by data file name \
will be used for out, bad, and dis files.
view release on metacpan or search on metacpan
t/connect.t view on Meta::CPAN
use warnings;
=head1 SYNOPSIS
In order to run these tests, you'll need to set your MySQL slave access
credentials in %ENV.
For example:
export SLAVE_DSN="dbi:mysql:database=my_database;host=my_db_hostname"
export SLAVE_USER=replication_user
view release on metacpan or search on metacpan
lib/DBIx/MyServer.pm view on Meta::CPAN
If you are subclassing C<DBIx::MyParse>, the way C<DBIx::MyParse::DBI> does, to establish a connection you call:
=item C<< $myserver->handshake() >>
which completes the handshake between the two parties. The return value will be C<undef> if some I/O error
occured, or the result of the client authorization routine. When the client sends its credentials, the
module will call:
=item C<< $myserver->authorize($remote_host, $username, $database) >>
whose default action is to accept only localhost connections regardless of username or password. You should
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
print FH<<STUB;
# named_dsn.conf
# This is the stub configuration file for DBIx::NamedDSN (version
# 0.01). Use this file to define your data source names and
# connection strings and optional login credentials.
# This file consists of up to four tab-separated columns. The first
# column is the unique name given to this configuration. This should
# be a single word which matches the perl regexp /^\w+\$/. This name
# is what you refer to in your programs when you want to connect to
view release on metacpan or search on metacpan
README.MySQL view on Meta::CPAN
In order to test DBIx::ORM::Declarative against a MySQL database, you need
to install the tables in the files t/dod_test.mysql.sql and
t/join_test.mysql.sql into a database, and update t/mysqlinfo.pl to reflect
the appropriate access credentials. For example, if you set up a database
with a name of 'dod_test' on your local machine, and give access to the
'dod_test' user with a password of 'dod_test', just uncommenting the
declarations in t/mysqlinfo.pl should do the trick.
You can install the tables by giving t/dod_test.mysql.sql and
view release on metacpan or search on metacpan
lib/DBIx/PgLink.pm view on Meta::CPAN
=item *
Mapping between database accounts
Can connect with different credentials for each PostgreSQL user.
=item *
Additional functionality for DBI
view release on metacpan or search on metacpan
lib/DBIx/QueryByName.pm view on Meta::CPAN
# Store information on how to open a database session
sub connect {
my ($self,$session,@params) = @_;
my $log = get_logger();
$log->logcroak("undefined session argument in connect") if (!defined $session);
$self->_dbh_pool()->add_credentials($session,@params);
return $self;
}
# Call dbi's quote()
sub quote {
view release on metacpan or search on metacpan
lib/DBIx/QuickORM.pm view on Meta::CPAN
=head1 RECIPES
=head2 DEFINE DB LATER
In some cases you may want to define your orm/schema before you have your
database credentials. Then you want to add the database later in an app/script
bootstrap process.
Schema:
package My::Schema;
lib/DBIx/QuickORM.pm view on Meta::CPAN
=item C<creds sub { return \%CREDS }>
Allows you to provide a coderef that will return a hashref with all the
necessary database connection fields.
This is mainly useful if you credentials are in an encrypted YAML or JSON file
and you have a method to decrypt and read it returning it as a hash.
db mydb => sub {
creds sub { ... };
};
lib/DBIx/QuickORM.pm view on Meta::CPAN
};
=item C<< server $NAME => sub { ... } >>
Used to define a server with multiple databases. This is a way to avoid
re-specifying credentials for each database you connect to.
You can use C<< db('server_name.db_name') >> to fetch the database.
Basically this allows you to specify any database fields once in the server, then
define any number of databases that inherit them.
view release on metacpan or search on metacpan
examples/lib/DB.pm view on Meta::CPAN
use strict;
use warnings;
use base qw( DBIx::TNDBO );
sub credentials {
my ($database) = @_;
return {
user => 'dylan',
pass => 'nalyd',
driver => 'mysql',
view release on metacpan or search on metacpan
lib/DBIx/TempDB.pm view on Meta::CPAN
use Test::More;
use DBIx::TempDB;
use DBI;
# provide credentials with environment variables
plan skip_all => 'TEST_PG_DSN=postgresql://postgres@localhost' unless $ENV{TEST_PG_DSN};
# create a temp database
my $tmpdb = DBIx::TempDB->new($ENV{TEST_PG_DSN});
view release on metacpan or search on metacpan
lib/DBIx/VersionedSubs.pm view on Meta::CPAN
$package;
};
=head2 C<< Package->connect DSN,User,Pass,Options >>
Connects to the database with the credentials given.
If called in void context, stores the DBI handle in the
C<dbh> accessor, otherwise returns the DBI handle.
If you already have an existing database handle, just
view release on metacpan or search on metacpan
lib/DBIx/XHTML_Table.pm view on Meta::CPAN
=head1 SYNOPSIS
use DBIx::XHTML_Table;
# database credentials - fill in the blanks
my ($data_source,$usr,$pass) = ();
my $table = DBIx::XHTML_Table->new($data_source,$usr,$pass);
$table->exec_query("
lib/DBIx/XHTML_Table.pm view on Meta::CPAN
=over 4
=item B<style_1>
$obj_ref = new DBIx::XHTML_Table(@credentials[,$attribs])
Note - all optional arguments are denoted inside brackets.
The constructor will simply pass the credentials to the DBI::connect
method - read the DBI documentation as well as the docs for your
corresponding DBI driver module (DBD::Oracle, DBD::Sybase,
DBD::mysql, etc).
# MySQL example
view release on metacpan or search on metacpan
lib/DCE/Perl/RPC.pm view on Meta::CPAN
############################################################################
# rpc_co_hdr composes the 16-bytes common DCE RPC header that must present #
# in all conection oriented DCE RPC messages. It takes four arguments: #
# 1) PDU type; 2) PDU flags; 3) size of the PDU part that is specific to #
# the PDU type; 4) size of the authentication credentials. #
# This function is an internal function. It is not supposed to be called #
# from the outside world. #
############################################################################
sub rpc_co_hdr($$$$)
{
lib/DCE/Perl/RPC.pm view on Meta::CPAN
# rpc_bind composes the DCE RPC bind PDU. To make things simple, it #
# assumes the PDU context list only has one element. It takes four #
# arguments: 1) Presentation Context Id; 2) Abstract Syntax #
# concatenated with interface version; 3) list of transfer syntax #
# concatenated with interface version; 4) authentication #
# credentials. #
#####################################################################
sub rpc_bind($$$@$)
{
my $self = shift;
my $ctx_id = shift;
lib/DCE/Perl/RPC.pm view on Meta::CPAN
###########################################################################
# rpc_co_request composes the connection-oriented DCE RPC Request PDU. It #
# takes five arguments: 1) the stub; 2) the presentation context id; #
# 3) operation # within the interface; 4) object UUID; 5) authetication #
# credentials. The fourth argument can be "" if there is no UUID #
# associate with this request PDU. #
###########################################################################
sub rpc_co_request($$$$$$)
{
my ($self, $body, $ctx_id, $op_num, $uuid, $auth_value) = @_;
lib/DCE/Perl/RPC.pm view on Meta::CPAN
##########################################################################
# rpc_alt_ctx composes a DCE RPC alter_context PDU. alter_context PDU is #
# used to change the presentation syntax established by the earlier bind #
# PDU. Therefore it has similar format. However, there is no need for #
# authentication credentials. Like rpc_bind, we also assume the #
# presentation context list only has one element. #
##########################################################################
sub rpc_alt_ctx($$$@)
{
my $self = shift;
view release on metacpan or search on metacpan
login_base/login_base.xs view on Meta::CPAN
#else
goto not_there;
#endif
break;
case 'c':
if (strEQ(name, "credentials_private"))
#ifdef sec_login_credentials_private
return sec_login_credentials_private;
#else
goto not_there;
#endif
break;
case 'd':
view release on metacpan or search on metacpan
lib/DJabberd/Authen/DBI.pm view on Meta::CPAN
=head1 DESCRIPTION
This module implements the "check_cleartext" method of the Authen
module in DJabberd. Your database schema should support checking the
credentials in one query.
=head1 CONFIGURATION
The following keys are used in the configuration.
view release on metacpan or search on metacpan
This authentication plugin uses Dovecot's SASL mechanism
to validate user's credentials. By default it tries to
connect to /var/run/dovecot/auth-client socket and sub-
mits authentication challenge using Dovecot's protocol.
Only PLAIN mechanism works so far, should not be a prob-
lem over encrypted TLS channel which is already de-facto
view release on metacpan or search on metacpan
Whats it for?
============
DJabberd::Authen::SQLite - is a simple SQLite authentication plugin that uses
SQLite as a user credentials repository.
Installation
============
view release on metacpan or search on metacpan
lib/DJabberd/Stanza/SASL.pm view on Meta::CPAN
sub on_recv_from_server { die "unimplemented" }
## TODO:
## check number of auth failures, force deconnection, bad for t time §7.3.5 policy-violation
## Provide hooks for Authen:: modules to return details about errors:
## - credentials-expired
## - account-disabled
## - invalid-authzid
## - temporary-auth-failure
## these hooks should probably additions to parameters taken by GetPassword, CheckClearText
## right now all these errors results in not-authorized being returned
view release on metacpan or search on metacpan
lib/DMTF/CIM/WSMan.pm view on Meta::CPAN
=item C<< current_uri( [I<new_uri>] ) >>
Gets or sets the current untyped WBEM URI for resource access. Supported
schemes are 'wsman.wbem', 'wsman.wbems', 'http', and 'https'. This is the
preferred way to establish a connection with a specific host using specific
credentials (ie: C<< $wsm->current_uri( 'wsman.wbem://user:pass@example.com:623/' >> )
=item C<< current_wsman >>
Returns the L<DMTF::WSMan> object associated with the current URI
view release on metacpan or search on metacpan
lib/DMTF/WSMan.pm view on Meta::CPAN
my $self = LWP::UserAgent::new($class, @_);
$self->{ASSOCIATED_WSMAN_OBJECT}=$awo;
return($self);
}
sub get_basic_credentials
{
my $self=shift;
return($self->{ASSOCIATED_WSMAN_OBJECT}{Context}{user},$self->{ASSOCIATED_WSMAN_OBJECT}{Context}{pass});
}
}
view release on metacpan or search on metacpan
lib/DNS/EasyDNS.pm view on Meta::CPAN
$@ = 'HTTP request failed "'.$resp->status_line.'"';
return;
}
}
=item DNS::EasyDNS->get_basic_credentials();
Since EasyDNS object is an inheritted L<LWP::UserAgent>, it overrides
this UserAgent method for your convenience. It uses the credentials passed
in the constructor. There is no real reason to override, or call this.
sub get_basic_credentials { ($_[0]->{"username"}, $_[0]->{"password"}) }
=cut
sub get_basic_credentials { ($_[0]->{"username"}, $_[0]->{"password"}) }
#==============================================================================#
=back
view release on metacpan or search on metacpan
t/tlib/Test/NIOS.pl view on Meta::CPAN
<body>
<h1>Authorization Required</h1>
<p>This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
</body>
</html>
view release on metacpan or search on metacpan
lib/DNS/ZoneEdit.pm view on Meta::CPAN
$@ = 'HTTP Request failed: "'.$resp->status_line.'"';
return;
}
}
=item get_basic_credentials();
Since a ZoneEdit object is an subclass of C<LWP::UserAgent>, it overrides
this UserAgent method for your convenience. It uses the credentials passed
in the update method. There is no real reason to call, or override this method.
=cut
sub get_basic_credentials { ($_[0]->{"username"}, $_[0]->{"password"}) }
=back
=head1 NOTES
view release on metacpan or search on metacpan
CAB/Server/HTTP/UNIX.pm view on Meta::CPAN
use File::Basename qw(basename);
use DTA::CAB::Utils qw(:proc);
our @ISA = qw(HTTP::Daemon::ClientConn);
## ($pid,$uid,$gid) = $sock->peercred()
## + gets peer credentials; returns (-1,-1,-1) on failure
sub peercred {
my $sock = shift;
if ($sock->can('SO_PEERCRED')) {
my $buf = $sock->sockopt($sock->SO_PEERCRED);
return unpack('lll',$buf);
CAB/Server/HTTP/UNIX.pm view on Meta::CPAN
${*$sock}{'peerenv'} = \%env;
}
## $str = $sock->peerstr()
## $str = $sock->peerstr($uid,$gid,$pid)
## + returns stringified unix peer credentials: "${USER}.${GROUP}[${PID}]"
sub peerstr {
my ($sock,$pid,$uid,$gid) = @_;
($pid,$uid,$gid) = $sock->peercred() if (@_ < 4);
return (
(defined($uid) ? (getpwuid($uid)//'?') : '?')
CAB/Server/HTTP/UNIX.pm view on Meta::CPAN
);
}
## $host = peerhost()
## + for relayed connections, gets underlying TCP peer via socat environment
## + for unix connections, returns UNIX credentials as as for peerstr()
sub peerhost {
my $sock = shift;
##-- get UNIX socket credentials
my ($pid,$uid,$gid) = $sock->peercred();
if (defined($pid) && basename(pid_cmd($pid)//'?') eq 'socat') {
##-- get socat environment variable if applicable
my $env = $sock->peerenv();
return $env->{DTA_CAB_RELAY_PEERADDR} if ($env && $env->{DTA_CAB_RELAY_PEERADDR});
}
##-- return UNIX socket credentials
return $sock->peerstr($pid,$uid,$gid);
}
## $port = peerport()
## + for relayed connections, gets underlying TCP port via socat environment
## + for unix connections, returns socket path
sub peerport {
my $sock = shift;
##-- get UNIX socket credentials
my ($pid,$uid,$gid) = $sock->peercred();
if (defined($pid) && basename(pid_cmd($pid)//'?') eq 'socat') {
##-- get socat environment variable if applicable
my $env = $sock->peerenv();
return $env->{DTA_CAB_RELAY_PEERPORT} if ($env && $env->{DTA_CAB_RELAY_PEERPORT});
CAB/Server/HTTP/UNIX.pm view on Meta::CPAN
=item peercred
($pid,$uid,$gid) = $sock->peercred();
Gets UNIX socket peer credentials; returns (-1,-1,-1) on failure.
=item peerenv
\%env = $sock->peerenv();
\%env = $sock->peerenv($pid);
CAB/Server/HTTP/UNIX.pm view on Meta::CPAN
=item peerstr
$str = $sock->peerstr();
$str = $sock->peerstr($uid,$gid,$pid);
Returns stringified unix peer credentials, "${USER}.${GROUP}[${PID}]".
=item peerhost
$host = peerhost();
For relayed connections, gets underlying TCP peer via socat environment (INET emulation);
for unix connections, returns UNIX credentials as as for peerstr().
=item peerport
$port = peerport();
view release on metacpan or search on metacpan
lib/Daemonise.pm view on Meta::CPAN
At this point all required plugins for Dist::Zilla and modules to run tests
should be installed. Daemonise uses PGP signed github releases, so make sure your
git config user and email are setup correctly as well as a PGP key that matches
your git(hub) account email. Try Config::Identity for a PGP encrypted file of
your github account credentials in ~/.github for convenience.
Finally run:
dzil release
which will do all the work (build, test, sign, tag, update github, upload).
view release on metacpan or search on metacpan
lib/Dancer/Exception.pm view on Meta::CPAN
This method allows one to register custom exceptions, usable by Dancer users in
their route code (actually pretty much everywhere).
# simple exception
register_exception ('InvalidCredentials',
message_pattern => "invalid credentials : %s",
);
This registers a new custom exception. To use it, do:
raise InvalidCredentials => "user Herbert not found";
The exception message can be retrieved with the C<$exception-E<gt>message> method, and we'll be
C<"invalid credentials : user Herbert not found"> (see methods in L<Dancer::Exception::Base>)
# complex exception
register_exception ('InvalidLogin',
composed_from => [qw(Fatal InvalidCredentials)],
message_pattern => "wrong login or password",