search

Azure / Azure-Functions

1.11k stars 195 forks source link

Provide safe clock skew assumptions for Azure Functions #76

Open christopheranderson opened 7 years ago

christopheranderson commented 7 years ago

Certain distibuted applications use timestamp, with some assumption of clock skew, to help manage things. Given that users can't know what machines they are running on ahead of time to monitor/manage their own clock skew, we should consider providing an estimate.

Originated from Stack Overflow: http://stackoverflow.com/questions/40724637/are-there-any-reasonable-clock-skew-assumptions-when-using-azure-functions

lindydonna commented 7 years ago

@christopheranderson It looks like I mistakenly labeled this as a documentation issue. This is a feature, right?

tommck commented 2 years ago

Honestly, I think it's CRAZY for us to be dealing with the level of clock skew I'm seeing in Azure Functions. This problem has been solved for decades. Why do we not have the ability have a decently synchronized clock in PaaS?

I have an external service we're creating JWTs for and getting 403 errors because our tokens were created "in the future". That's pathetic. "Premium" services ought to include basic clock synchronization