Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sign and verify authToken per config expireInMinutes option #229

Open
epicmonkey opened this issue Jun 2, 2015 · 3 comments
Open

Sign and verify authToken per config expireInMinutes option #229

epicmonkey opened this issue Jun 2, 2015 · 3 comments
Milestone

Comments

@epicmonkey
Copy link
Member

Additionally we need to invalidate old tokens when user changes her password.

@epicmonkey epicmonkey added this to the Uncategorized milestone Jun 2, 2015
@epicmonkey epicmonkey modified the milestones: 0.2.0, Uncategorized Jun 2, 2015
@urbansheep
Copy link

It might be a useful added practice to let user know in Settings how many tokens are active and list them with last access date/time stamp (best case — with user agent, OS, ip and geoip location) so that potential breach could be identified.

@epicmonkey
Copy link
Member Author

Indeed! I've created a separate story for this: #230. Moving towards this will open flexible ways building Pepyatka applications, e.g. Import Twitter/RSS, whatever.

@urbansheep
Copy link

Yes, even though it's quite a lot of work, this leads to a couple of useful things that Friendfeed had (oAuth for apps and integrations) as well as those (quite critical for secure deployment) that Friendfeed never evolved far enough to develop (such as two-factor login).

@epicmonkey epicmonkey modified the milestones: 0.2.0, 0.4.0 Jun 3, 2015
@epicmonkey epicmonkey modified the milestones: 0.7.0, 0.4.0 Jul 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants