Go to the documentation of this file.
16 case AuthManager::ACTION_CREATE:
17 $needed = $captcha->needCreateAccountCaptcha(
$user ?:
new User() );
19 $captcha->setAction(
'accountcreate' );
20 LoggerFactory::getInstance(
'authevents' )
21 ->info(
'Captcha shown on account creation', [
22 'event' =>
'captcha.display',
23 'eventType' =>
'accountcreation',
27 case AuthManager::ACTION_LOGIN:
39 $session = $this->manager->getRequest()->getSession();
40 $sessionFlag = $session->get(
'ConfirmEdit:loginCaptchaPerUserTriggered' );
41 $suggestedUsername = $session->suggestLoginUsername();
43 $captcha->isBadLoginTriggered()
45 || $suggestedUsername && $captcha->isBadLoginPerUserTriggered( $suggestedUsername )
48 $captcha->setAction(
'badlogin' );
49 LoggerFactory::getInstance(
'authevents' )
50 ->info(
'Captcha shown on account creation', [
51 'event' =>
'captcha.display',
52 'eventType' =>
'accountcreation',
60 return [ $captcha->createAuthenticationRequest() ];
68 $username = AuthenticationRequest::getUsernameFromRequests( $reqs );
71 $captcha->isBadLoginPerUserTriggered(
$username ) :
false;
73 if ( $captcha->isBadLoginTriggered() || $isBadLoginPerUserTriggered ) {
74 $captcha->setAction(
'badlogin' );
75 $captcha->setTrigger(
"post-badlogin login '$username'" );
77 LoggerFactory::getInstance(
'authevents' )->info(
'Captcha submitted on login', [
78 'event' =>
'captcha.submit',
79 'eventType' =>
'login',
84 if ( $isBadLoginPerUserTriggered || $isBadLoginPerUserTriggered ===
null ) {
85 $session = $this->manager->getRequest()->getSession();
86 $session->set(
'ConfirmEdit:loginCaptchaPerUserTriggered',
true );
97 if ( $captcha->needCreateAccountCaptcha( $creator ) ) {
99 $captcha->setAction(
'accountcreate' );
100 $captcha->setTrigger(
"new account '$username'" );
102 LoggerFactory::getInstance(
'authevents' )->info(
'Captcha submitted on account creation', [
103 'event' =>
'captcha.submit',
104 'eventType' =>
'accountcreation',
108 return $this->
makeError(
'captcha-createaccount-fail', $captcha );
117 case AuthenticationResponse::PASS:
118 case AuthenticationResponse::RESTART:
119 $session = $this->manager->getRequest()->getSession();
120 $session->remove(
'ConfirmEdit:loginCaptchaPerUserTriggered' );
121 $captcha->resetBadLoginCounter(
$user ?
$user->getName() :
null );
123 case AuthenticationResponse::FAIL:
124 $captcha->increaseBadLoginCounter(
$user ?
$user->getName() :
null );
139 $req = AuthenticationRequest::getRequestByClass( $reqs,
return true to allow those checks to and false if checking is done & $user
makeError( $message, SimpleCaptcha $captcha)
this hook is for auditing only $req
static newFatal( $message)
Factory function for fatal errors.
static newFromName( $name, $validate='valid')
Static factory method for creation from username.
postAuthentication( $user, AuthenticationResponse $response)
Post-login callback.
static getInstance()
Get the global Captcha instance.
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
passCaptchaLimited( $index, $word, User $user)
Checks, if the user reached the amount of false CAPTCHAs and give him some vacation or run self::pass...
getAuthenticationRequests( $action, array $options)
Return the applicable list of AuthenticationRequests.
testForAccountCreation( $user, $creator, array $reqs)
Determine whether an account creation may begin.
as see the revision history and available at free of to any person obtaining a copy of this software and associated documentation to deal in the Software without including without limitation the rights to use
The wiki should then use memcached to cache various data To use multiple just add more items to the array To increase the weight of a make its entry a array("192.168.0.1:11211", 2))
this hook is for auditing only or null if authentication failed before getting that far or null if we can t even determine that When $user is not null
testForAuthentication(array $reqs)
Determine whether an authentication may begin.
static newGood( $value=null)
Factory function for good results.
Demo CAPTCHA (not for production usage) and base class for real CAPTCHAs.
getError()
Return the error from the last passCaptcha* call.
this hook is for auditing only $response
null means default in associative array with keys and values unescaped Should be merged with default with a value of false meaning to suppress the attribute in associative array with keys and values unescaped & $options
verifyCaptcha(SimpleCaptcha $captcha, array $reqs, User $user)
Verify submitted captcha.
MediaWiki Logger LoggerFactory implements a PSR[0] compatible message logging system Named Psr Log LoggerInterface instances can be obtained from the MediaWiki Logger LoggerFactory::getInstance() static method. MediaWiki\Logger\LoggerFactory expects a class implementing the MediaWiki\Logger\Spi interface to act as a factory for new Psr\Log\LoggerInterface instances. The "Spi" in MediaWiki\Logger\Spi stands for "service provider interface". An SPI is an API intended to be implemented or extended by a third party. This software design pattern is intended to enable framework extension and replaceable components. It is specifically used in the MediaWiki\Logger\LoggerFactory service to allow alternate PSR-3 logging implementations to be easily integrated with MediaWiki. The service provider interface allows the backend logging library to be implemented in multiple ways. The $wgMWLoggerDefaultSpi global provides the classname of the default MediaWiki\Logger\Spi implementation to be loaded at runtime. This can either be the name of a class implementing the MediaWiki\Logger\Spi with a zero argument const ructor or a callable that will return an MediaWiki\Logger\Spi instance. Alternately the MediaWiki\Logger\LoggerFactory MediaWiki Logger LoggerFactory
you have access to all of the normal MediaWiki so you can get a DB use the etc For full docs on the Maintenance class
either a unescaped string or a HtmlArmor object after in associative array form externallinks including delete and has completed for all link tables whether this was an auto creation use $formDescriptor instead default is conds Array Extra conditions for the No matching items in log is displayed if loglist is empty msgKey Array If you want a nice box with a set this to the key of the message First element is the message additional optional elements are parameters for the key that are processed with wfMessage() -> params() ->parseAsBlock() - offset Set to overwrite offset parameter in $wgRequest set to '' to unset offset - wrap String Wrap the message in html(usually something like "<
The User object encapsulates all of the user-specific settings (user_id, name, rights,...
this hook is for auditing only or null if authentication failed before getting that far $username