Allow customizing lifetime of 2FA codes for built in providers #133

suhasj · 2014-06-20T21:11:28Z

Changing the time for which the 2FA codes are valid is not possibly right now. Need to look into that

rustd · 2014-09-15T22:07:04Z

Each provider will have its own lifetime

suhasj · 2015-04-28T22:31:38Z

Removing milestone for it to be triaged. Need to review this request from a security perspective.

HaoK · 2015-05-05T00:04:54Z

Probably can just add a Timespan expiries to the options per provider, one knob per TokenProvider class seems reasonable, @blowdart thoughts?

blowdart · 2015-05-05T19:50:15Z

Timespan works for me

HaoK · 2015-06-08T18:14:14Z

Dupe of #465

rustd added this to the 3.0.0-rc1 milestone Sep 15, 2014

rustd assigned HaoK Sep 15, 2014

HaoK assigned suhasj and unassigned HaoK Nov 10, 2014

suhasj modified the milestones: 3.0.0-rc1, 3.0.0-beta2 Dec 1, 2014

blowdart mentioned this issue Dec 8, 2014

Expire duration for confirm email, phone number and reset password #282

Closed

suhasj modified the milestones: 3.0.0-RTM, 3.0.0-rc1 Jan 6, 2015

rustd modified the milestones: 3.0.0-RTM, 3.0.0-rc1 Jan 16, 2015

suhasj modified the milestones: 3.0.0-RTM, 3.0.0-rc1 Mar 16, 2015

suhasj removed this from the 3.0.0-beta5 milestone Apr 28, 2015

suhasj removed their assignment Apr 28, 2015

HaoK self-assigned this May 5, 2015

rustd added this to the 3.0.0-beta5 milestone May 11, 2015

rustd modified the milestones: 3.0.0-beta5, 3.0.0-beta6 Jun 1, 2015

HaoK closed this as completed Jun 8, 2015

rustd added the 3 - Done label Jul 24, 2015

Provide feedback