Skip to content
This repository has been archived by the owner. It is now read-only.

Need ability to force a user to reset their password #698

Closed
pdehaan opened this issue Apr 29, 2014 · 7 comments
Closed

Need ability to force a user to reset their password #698

pdehaan opened this issue Apr 29, 2014 · 7 comments

Comments

@pdehaan
Copy link
Contributor

@pdehaan pdehaan commented Apr 29, 2014

Random use case:
Something like HeartBleed 2.0 comes out in the wild. We patch our certs and make sure everything is clean, but we want to proactively make users change their passwords (versus passively sending an email to everybody and ASK them to change them).

Not sure if we can force the user's account into a state where they need to reset their password after their next successful login, or if we halt syncing and everything else and throw up a doorhanger saying "Please reset your password to continue synching".

Discuss.

@jkufner
Copy link

@jkufner jkufner commented Apr 30, 2014

Do not halt syncing. In many cases it is better to continue even if security may be compromised. Especialy when user is away from home and any problem can be very hard to solve.

@rfk rfk changed the title Need ability to force a user to reset their password Need ability to force a user to reset their password? May 6, 2014
@pdehaan pdehaan added this to the z-later milestone May 6, 2014
@pdehaan
Copy link
Contributor Author

@pdehaan pdehaan commented May 6, 2014

Lets email this to the group and get a discussion goin.

@rfk rfk added the z-later label Mar 9, 2015
@rfk rfk removed this from the z-later milestone Jun 3, 2015
@rfk rfk changed the title Need ability to force a user to reset their password? Need ability to force a user to reset their password Jun 18, 2015
@rfk
Copy link
Member

@rfk rfk commented Jun 18, 2015

We should definitely do this, removing question-mark from title and moving into "ready" (after being inspired/terrified by the recent lastpass breach). I think we could actually do a really simple variant of this as follows:

  • Introduce a new error code for "you have to change your password"
  • Make a config option giving the date of the last security event, defaulting to zero
  • On login, check whether account.verifierSetAt < config.timestampOfLastSecurityApocalypse and error out if so
  • Add new UI for all this in content-server and android (oh, did I say "simple"..?)

We could leave existing sessionTokens alone, and allow the user to proceed via password change rather than outright password reset, which should prevent any funny business with existing sync devices suddenly disconnecting.

@rfk
Copy link
Member

@rfk rfk commented Jun 18, 2015

/cc @shane-tomlinson who mentioned this to me the other day.

@shane-tomlinson
Copy link
Member

@shane-tomlinson shane-tomlinson commented Jun 18, 2015

Add new UI for all this in content-server and android (oh, did I say "simple"..?)

Don't forget about FxOS.

@rfk
Copy link
Member

@rfk rfk commented Jun 18, 2015

Ugh, I always forget abut FxOS.

@rfk
Copy link
Member

@rfk rfk commented Nov 18, 2015

Closing out this old bug, we'll revisit it through product planning process in Aha

@rfk rfk closed this Nov 18, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants