Might be more of a self-rant.. We’re developing an application with token-based authentication.
It’s a big an complex authentication model and flow, which we wrapped up a month ago. All of us very proud of it.

All of a sudden none of it worked.
We debugged for days, there were no errors or anything to trace what was happening.

Today we realized that we set the expiration of the token to 20 years.
Aaaand the expiration time is later on converted to epoch.

Guess what happens when you try to use a value > 2 147 483 647 in C#? Stuff blows up, cuz that’s the limit of an int32.

So yeah, feels good having prepared for the Y2K38 bug already, even though we’ll be replaced by AI writing better software than my dumb ass by then.

(To be fair, it was hidden in Microsoft Owin, which could use some error handling and/or proper messages..)

Add Comment