MediaWiki REL1_28
Go to the documentation of this file.
22namespace MediaWiki\Auth;
34 public function continueSecondaryAuthentication( $user, array $reqs ) {
35 throw new \BadMethodCallException( __METHOD__ . ' is not implemented.' );
36 }
39 }
42 return true;
43 }
51 $reqs = $this->getAuthenticationRequests(
52 AuthManager::ACTION_REMOVE, [ 'username' => $username ]
53 );
54 foreach ( $reqs as $req ) {
55 $req->username = $username;
57 }
58 }
61 AuthenticationRequest $req, $checkData = true
62 ) {
63 return \StatusValue::newGood( 'ignored' );
64 }
69 public function testForAccountCreation( $user, $creator, array $reqs ) {
70 return \StatusValue::newGood();
71 }
73 public function continueSecondaryAccountCreation( $user, $creator, array $reqs ) {
74 throw new \BadMethodCallException( __METHOD__ . ' is not implemented.' );
75 }
77 public function postAccountCreation( $user, $creator, AuthenticationResponse $response ) {
78 }
80 public function testUserForCreation( $user, $autocreate, array $options = [] ) {
81 return \StatusValue::newGood();
82 }
84 public function autoCreatedAccount( $user, $source ) {
85 }
A base class that implements some of the boilerplate for an AuthenticationProvider.
A base class that implements some of the boilerplate for a SecondaryAuthenticationProvider.
providerAllowsPropertyChange( $property)
Determine whether a property can change.
testUserForCreation( $user, $autocreate, array $options=[])
Determine whether an account may be created.
postAccountCreation( $user, $creator, AuthenticationResponse $response)
Post-creation callback.
postAuthentication( $user, AuthenticationResponse $response)
Post-login callback.
continueSecondaryAuthentication( $user, array $reqs)
Continue an authentication flow.
continueSecondaryAccountCreation( $user, $creator, array $reqs)
Continue an authentication flow.
testForAccountCreation( $user, $creator, array $reqs)
Determine whether an account creation may begin.
providerRevokeAccessForUser( $username)
Revoke the user's credentials.This may cause the user to no longer exist for the provider,...
providerAllowsAuthenticationDataChange(AuthenticationRequest $req, $checkData=true)
Validate a change of authentication data (e.g.
providerChangeAuthenticationData(AuthenticationRequest $req)
Change or remove authentication data (e.g.
Remove a user's credentials.
This is a value object for authentication requests.
This is a value object to hold authentication response data.
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such as
this hook is for auditing only $req
Definition hooks.txt:1010
the array() calling protocol came about after MediaWiki 1.4rc1.
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set and then return false from the hook function Ensure you consume the ChangeTagAfterDelete hook to carry out custom deletion actions as context called by AbstractContent::getParserOutput May be used to override the normal model specific rendering of page content as context as context $options
Definition hooks.txt:1096
this hook is for auditing only or null if authentication failed before getting that far $username
Definition hooks.txt:807
this hook is for auditing only $response
Definition hooks.txt:805
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:37
getAuthenticationRequests( $action, array $options)
Return the applicable list of AuthenticationRequests.
A secondary provider mostly acts when the submitted authentication data has already been associated t...