So because of the architectural differences between the two extensions, I figured it'd just be easier to make a tracking bug and have bugs for all the things OATHAuth is missing that TwoFactorAuthentication has. Then I'll re-fix those things one-by-one rather than attempting some kind of massive code merge.
Description
Description
Details
Details
- Reference
- bz53192
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Parent5446 | T55192 Merge Extension:TwoFactorAuthentication into Extension:OATHAuth | |||
| Resolved | Parent5446 | T55194 Make authentication window size and leniency configurable | |||
| Resolved | Parent5446 | T55195 OATH token input should be on a separate page | |||
| Resolved | Parent5446 | T55196 Used OATH should be cached to avoid replay attacks | |||
| Open | Feature | None | T55197 OATH should use $wgSecureLogin | ||
| Resolved | RyanLane | T55198 E:OATHAuth needs to be friendly with other authn extensions on the login page |
Event Timeline
Comment Actions
Is there just T55197 left to do here?
Or do we still have other features/improvements to gain?
Comment Actions
It should be just that. I filed a bug for every difference between the two at the time.
Comment Actions
@Aklapper I have seen this. So we can now archive the extension since a patch set is already in place, no?
Comment Actions
Can you link to the merged commit you refer to that fixed T55197? That task is open and blocking this task.
Comment Actions
So we can now archive the extension since a patch set is already in place, no?
tracked at T178770