* 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
The following sniffs are failing and were disabled:
* MediaWiki.Files.ClassMatchesFilename.NotMatch
* MediaWiki.Files.ClassMatchesFilename.WrongCase
Change-Id: I4e569fbf4cb6743a3b548b7d5db73137786355c2
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
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