Priya Nandakumar

Tokens and schedules — JWT verification, cron semantics

Priya covers the two places where a system trusts something it did not compute: a token it was handed, and a schedule it was configured with.

Both fail quietly. A JWT whose signature nobody checked decodes exactly like one that was verified, and a cron expression with the wrong field count runs on a timetable nobody intended. The pages under this byline spend their length on the step that catches it rather than on the syntax.

The cron work leans on running the expressions and reading back what the parser matched, since the day-of-month and day-of-week fields are OR-ed rather than AND-ed and no amount of reading the line aloud makes that visible.

What this byline is strict about

12 posts under this byline

All jwt guides →All cron guides →

Withuse publishes under three bylines, listed on the authors page. Each one owns a beat and is answerable for it; none of them claims an employer, a degree or a job history, because none of that is what makes a page on this site worth trusting. What does is on the about page: every claim is run before it is written, the runtime version is named, and corrections are dated and kept.