MediaWiki  1.29.1
AbstractAuthenticationProviderTest.php
Go to the documentation of this file.
1 <?php
2 
3 namespace MediaWiki\Auth;
4 
5 use Wikimedia\TestingAccessWrapper;
6 
13  $provider = $this->getMockForAbstractClass( AbstractAuthenticationProvider::class );
14  $providerPriv = TestingAccessWrapper::newFromObject( $provider );
15 
16  $obj = $this->getMockForAbstractClass( 'Psr\Log\LoggerInterface' );
17  $provider->setLogger( $obj );
18  $this->assertSame( $obj, $providerPriv->logger, 'setLogger' );
19 
20  $obj = AuthManager::singleton();
21  $provider->setManager( $obj );
22  $this->assertSame( $obj, $providerPriv->manager, 'setManager' );
23 
24  $obj = $this->getMockForAbstractClass( 'Config' );
25  $provider->setConfig( $obj );
26  $this->assertSame( $obj, $providerPriv->config, 'setConfig' );
27 
28  $this->assertType( 'string', $provider->getUniqueId(), 'getUniqueId' );
29  }
30 }
use
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
Definition: MIT-LICENSE.txt:10
php
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
Definition: injection.txt:35
MediaWikiTestCase
Definition: MediaWikiTestCase.php:13
MediaWiki\Auth\AbstractAuthenticationProviderTest
AuthManager MediaWiki\Auth\AbstractAuthenticationProvider.
Definition: AbstractAuthenticationProviderTest.php:11
vulnerability
storage can be distributed across multiple and multiple web servers can use the same cache cluster *********************W A R N I N G ***********************Memcached has no security or authentication Please ensure that your server is appropriately and that the anyone on the internet can put data into and read data from your cache An attacker familiar with MediaWiki internals could use this to steal passwords and email or to make themselves a sysop and install malicious javascript on the site There may be other types of vulnerability
Definition: memcached.txt:43
MediaWiki\Auth\AuthManager\singleton
static singleton()
Get the global AuthManager.
Definition: AuthManager.php:146
class
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
Definition: maintenance.txt:52
MediaWikiTestCase\assertType
assertType( $type, $actual, $message='')
Asserts the type of the provided value.
Definition: MediaWikiTestCase.php:1605
MediaWiki\Auth
Definition: AbstractAuthenticationProvider.php:22
MediaWiki\Auth\AbstractAuthenticationProviderTest\testAbstractAuthenticationProvider
testAbstractAuthenticationProvider()
Definition: AbstractAuthenticationProviderTest.php:12