What is Basic Authentication?
An HTTP authentication scheme that sends a Base64-encoded username and password with each request.
Definition
HTTP Basic Authentication is a simple authentication method where the client sends a username and password encoded in Base64 in the Authorization header: "Authorization: Basic dXNlcjpwYXNz" (which decodes to "user:pass"). While easy to implement, it is only secure when used over HTTPS, as Base64 encoding is trivially reversible. It is commonly used for simple API authentication and webhook endpoint protection.
Simple Analogy
Like a bouncer at a club who asks for your name and password at the door — simple and straightforward, but anyone who overhears can repeat them, so you need a private conversation (HTTPS).
Why It Matters
Basic Authentication is a simple way to protect your cron job endpoints from unauthorized access. If your endpoint is publicly accessible, anyone who discovers the URL could trigger your job. Adding Basic Auth ensures only CronJobPro (with the correct credentials) can call the endpoint.
How to Verify
Test with curl: `curl -u username:password https://your-endpoint.com`. In CronJobPro, configure the username and password in job settings. If you receive 401 Unauthorized, the credentials may be wrong. Verify your server is configured to require Basic Auth on the endpoint.
Common Mistakes
Using Basic Auth over HTTP (not HTTPS), exposing credentials in plain text. Using weak passwords. Not rotating credentials periodically. Implementing Basic Auth on the client side only, without enforcing it on the server.
Best Practices
Only use Basic Auth over HTTPS. Use strong, randomly generated passwords. Consider upgrading to bearer token or API key authentication for production systems. If using Basic Auth, store credentials in CronJobPro's secure credential storage.
HTTP Methods Guide
Learn about HTTP methods
Try it free →Frequently Asked Questions
What is Basic Authentication?
HTTP Basic Authentication is a simple authentication method where the client sends a username and password encoded in Base64 in the Authorization header: "Authorization: Basic dXNlcjpwYXNz" (which decodes to "user:pass"). While easy to implement, it is only secure when used over HTTPS, as Base64 encoding is trivially reversible. It is commonly used for simple API authentication and webhook endpoint protection.
Why does Basic Authentication matter for cron jobs?
Basic Authentication is a simple way to protect your cron job endpoints from unauthorized access. If your endpoint is publicly accessible, anyone who discovers the URL could trigger your job. Adding Basic Auth ensures only CronJobPro (with the correct credentials) can call the endpoint.
What are best practices for Basic Authentication?
Only use Basic Auth over HTTPS. Use strong, randomly generated passwords. Consider upgrading to bearer token or API key authentication for production systems. If using Basic Auth, store credentials in CronJobPro's secure credential storage.
Related Terms
Bearer Token
An access token sent in the Authorization header to authenticate HTTP requests.
Authentication
Verifying the identity of a user or system making a request to your endpoint.
API Key
A unique string used to identify and authenticate a client making API requests.
HTTPS
The secure version of HTTP that encrypts all communication between client and server.