Page MenuHomePhabricator

configure oauth timestamp leeway per-environment
Open, Needs TriagePublic

Description

As discussed in T243137, the fixed oauth timestamp leeway value we're using isn't always adequate to allow authentication to succeed in local development environments. Instead of using a hardcoded value, we should add an environment variable and a django setting to configure this value for different environments via docker-compose.

Event Timeline

Does this need to be a priority or can it sit in the backlog for now?

This isn't an immediate priority for us, but if it crops up again on a regular basis, especially for TWL developers, we'll prioritise a fix.