MediaWiki  1.28.1
AbstractSecondaryAuthenticationProvider.php
Go to the documentation of this file.
1 <?php
22 namespace MediaWiki\Auth;
23 
32 {
33 
34  public function continueSecondaryAuthentication( $user, array $reqs ) {
35  throw new \BadMethodCallException( __METHOD__ . ' is not implemented.' );
36  }
37 
39  }
40 
42  return true;
43  }
44 
51  $reqs = $this->getAuthenticationRequests(
52  AuthManager::ACTION_REMOVE, [ 'username' => $username ]
53  );
54  foreach ( $reqs as $req ) {
55  $req->username = $username;
56  $this->providerChangeAuthenticationData( $req );
57  }
58  }
59 
61  AuthenticationRequest $req, $checkData = true
62  ) {
63  return \StatusValue::newGood( 'ignored' );
64  }
65 
67  }
68 
69  public function testForAccountCreation( $user, $creator, array $reqs ) {
70  return \StatusValue::newGood();
71  }
72 
73  public function continueSecondaryAccountCreation( $user, $creator, array $reqs ) {
74  throw new \BadMethodCallException( __METHOD__ . ' is not implemented.' );
75  }
76 
78  }
79 
80  public function testUserForCreation( $user, $autocreate, array $options = [] ) {
81  return \StatusValue::newGood();
82  }
83 
84  public function autoCreatedAccount( $user, $source ) {
85  }
86 }
postAuthentication($user, AuthenticationResponse $response)
Post-login callback.
the array() calling protocol came about after MediaWiki 1.4rc1.
getAuthenticationRequests($action, array $options)
Return the applicable list of AuthenticationRequests.
$property
continueSecondaryAuthentication($user, array $reqs)
Continue an authentication flow.
providerRevokeAccessForUser($username)
Revoke the user's credentials.This may cause the user to no longer exist for the provider, or the user may continue to exist in a "disabled" state.The intention is that the named account will never again be usable for normal login (i.e. there is no way to undo the revocation of access).
$source
providerAllowsPropertyChange($property)
Determine whether a property can change.
This is a value object to hold authentication response data.
this hook is for auditing only $response
Definition: hooks.txt:802
continueSecondaryAccountCreation($user, $creator, array $reqs)
Continue an authentication flow.
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:1046
testUserForCreation($user, $autocreate, array $options=[])
Determine whether an account may be created.
providerChangeAuthenticationData(AuthenticationRequest $req)
Change or remove authentication data (e.g.
A base class that implements some of the boilerplate for a SecondaryAuthenticationProvider.
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
Definition: distributors.txt:9
please add to it if you re going to add events to the MediaWiki code where normally authentication against an external auth plugin would be creating a local account $user
Definition: hooks.txt:242
providerAllowsAuthenticationDataChange(AuthenticationRequest $req, $checkData=true)
Validate a change of authentication data (e.g.
testForAccountCreation($user, $creator, array $reqs)
Determine whether an account creation may begin.
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
this hook is for auditing only $req
Definition: hooks.txt:1007
this hook is for auditing only or null if authentication failed before getting that far $username
Definition: hooks.txt:802
postAccountCreation($user, $creator, AuthenticationResponse $response)
Post-creation callback.
A base class that implements some of the boilerplate for an AuthenticationProvider.
const ACTION_REMOVE
Remove a user's credentials.
This is a value object for authentication requests.
A secondary provider mostly acts when the submitted authentication data has already been associated t...