Check session_expires

[mushketyk]

I am not sure that I made it right, but please write if I am on the right way.
#2344

[Changaco]

@ivanmushketyk I guess my answer on IRC wasn't clear enough. We currently don't modify schema.sql in PRs, if you want to change the DB schema then you need to create a branch.sql that makes the change. The person who merges your PR will run the branch.sql on the production DB, before or after deploying depending on what it does.

In this case it would be before deploying, and the branch.sql would contain something like this:

ALTER TABLE participants ALTER COLUMN session_expires SET DEFAULT CURRENT_TIMESTAMP + INTERVAL '6 hours';

[mushketyk]

@Changaco Thank you. Now I got it.
What about the rest? Is session checking implemented correctly?

[Changaco]

@ivanmushketyk

• pytz.utc.localize(datetime.datetime.now()) is wrong, it should be pytz.utc.localize(datetime.datetime.utcnow())
• I think it would be better to check session_expires in the Participant.from_session_token() class method instead of in the authentication.inbound() hook.

[mushketyk]

@Changaco Fixed. Could you please take a look?

[Changaco]

Looks good.