1. Why OAuth token management needs to be part of #IAM program >> Twitter Apps Can Still Tweet Despite Password Reset - bit.ly/WskOxJ
  2. My name is Paul and I am a compulsive application authorizer #hiPaul http://pic.twitter.com/4HUFkAyc
  3. @paulmadsen Not judging. But definitely going to use you as a case study. #InThisRoom...
  4. .@paulmadsen The concern re. no autorevoke is a hacked password being used to authorize app, which (unknowingly) continues to have access
  5. @NishantK but existing apps were issued their tokens when no risk present. So, why not instead not issue new tokens until pwd changed?
  6. @paulmadsen Assumes you know exactly when account was compromised. Not always clear.
  7. @NishantK so should Twitter revoke all 54 of my issued tokens?
  8. @paulmadsen If password was compromised, additional tokens could have been generated with rogue app - Surely best to do a token reset?
  9. @dchristiansen I had 54 extant tokens at the time of the (potential) compromise. What price security? /cc @NishantK
  10. @paulmadsen @NishantK Agreed. Site could display the date of when an app was trusted. Highlighting any changed around the time of the breach
  11. @paulmadsen @NishantK The alternative was me weeding out my trusted app list and regenerating tokens
  12. @paulmadsen Given that you are the edge case that I am NOT going to design my security protocol around (seriously, 54?), I say yes.

Did you find this story interesting? Be the first to or comment.

Liked!

Nishant Kaushik

Chief Architect @ Identropy | Solver of Problems | Passion for Identity, Tech, Family, Travel, Sports (esp. NYY/NYG/ManU) | Recommended by 4 out of 5 Identirati

Total views
29

Storify

@Storify