You can avoid having to authenticate the request from cron at all.
- Create a backend; let it be named
cronbackend. Mark it as private. - Move your handler that cron needs to touch to that backend.
- Now the URL has changed: instead of
myapp.appspot.com/url it has become cronbackend-dot-myapp.appspot.com/url. Let cron use this URL.
Since your backend is private, it is not exposed to the outside world at all; only your frontend (your application), your cron, or manager of your queues can access it. Also, handlers on a backend can run for significantly longer.
Note that a backend and a frontend look like separate apps, are deployed independently, and billed separately. This allows for added flexibility, though.