Commit graph

8 commits

Author SHA1 Message Date
Kunal Mehta 7451a5df33 Move classes to includes/
Change-Id: I2d2a917e5a22f88dc644eb3c33f775642728e1f4
2018-04-09 00:51:39 -07:00
Umherirrender 00805b4cf8 Fix parameter docs
* OATHAuthKey::$secret is accessed as array in getSecret
* OATHAuthUtils::getKeyMaterials returns an string, because the globals
are strings
* OATHUser::__construct make argument also nullable in @param
Change-Id: I61813012aa27a654b747cdf86af3616a33c5208c
2018-04-05 13:27:13 +02:00
libraryupgrader 46df6b13d4 build: Updating mediawiki/mediawiki-codesniffer to 14.1.0
And moved phpcs.xml to .phpcs.xml (T177256).

Change-Id: Iedc6222900f21df887735d84c1255d6fc1cd82ce
2017-10-21 04:27:16 +00:00
libraryupgrader 21300d1a14 build: Updating mediawiki/mediawiki-codesniffer to 0.12.0
The following sniffs are failing and were disabled:
* MediaWiki.Files.ClassMatchesFilename.NotMatch
* MediaWiki.Files.ClassMatchesFilename.WrongCase

Change-Id: I4e569fbf4cb6743a3b548b7d5db73137786355c2
2017-09-01 04:54:23 +00:00
Gergő Tisza 160daf2c05 Provide a stable method for checking whether a user has enabled OATH
This makes it possible to check from another extension whether the
user has strong login security, without depending on internals
which can change at any time.

(The TwoFactorEnabled hook was intended for something like this
but it operates on $wgUser which makes it useless for logins.)

Change-Id: Ie15c45c9b29de0a0f926c2467808ca144f05e866
2016-11-15 23:13:59 +00:00
Reedy 52686c04b7 Minor documentation updates
Update DatabaseBase type hint

Update some deprecated code usages

Change-Id: I86aa4507447040754d0c9f20171f7e22aed4a0cc
2016-10-02 12:25:59 +00:00
Reedy 9cceee17cc Clean up code style and docblocks
* array() -> []
* spacing fixes
* dirname( __FILE__ ) -> __DIR__
* Add phpcs style checks using latest mediawiki-codesniffer to keep
  things clean.

Co-Authored-By: Bryan Davis <bd808@wikimedia.org>
Change-Id: I95735f928d3e5d6ac9d2a10d92b40ed01cf2737c
2016-09-30 14:40:06 -06:00
csteipp a24d6adfbf Encrypt password when stored in user session
During the two-step login, users with OATH enabled need to have their
login details saved into their session while we prompt them for their
OATH code. This encrypts that data, so we don't write their user's
password into our session storage.

Change-Id: I9969871205ac5c438706df41ef1519cb4cd7a964
2016-03-30 21:23:48 -07:00