doc: add api authentication article (#412)

Signed-off-by: Aransiola Ayodele <[email protected]>

practices/api_authentication.md

@@ -0,0 +1,80 @@
+---
+slug: api-authentication
+stages:
+  - development
+short_description: API Authentication is the process of securely verifying and authenticating API requests. This article outlines best practices for setting API credentials and securing APIs.
+tags:
+  - api authentication
+  - api security
+  - headers
+  - api keys
+  - oauth
+  - tokens
+  - encryption
+  - development
+keywords:
+  - api authentication
+  - api security
+  - securing apis
+  - api credentials
+  - api keys
+  - oauth
+  - tokens
+  - encryption
+  - api headers
+author_github_username: CodeLeom
+---
+
+# API Authentication
+
+## What Is API Authentication?
+
+API authentication is the process of verifying the identity of an API client or user trying to access an API. It involves setting up secure methods for exchanging credentials between the client and the API server. Proper API authentication ensures that only authorized clients/users can access the API and perform actions, protecting the data and services from unauthorized access.
+
+In software development, securing APIs is very important for preventing data breaches and ensuring that applications interact with APIs in a secure medium.
+
+## The Need for API Authentication
+
+APIs are often a key gateway to sensitive data and services, so implementing secure authentication mechanisms is essential for:
+
+- **Ensuring Secure API Access**: Ensuring that only authorized users or systems can access the API helps protect against unauthorized usage or data exposure. You can implement [CORs](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) to prevent unauthorized domain from accessing your API. 
+
+- **Preventing Credential Leaks**: By using secure methods to pass credentials (like headers), you can avoid leaking sensitive information through logs or network sniffing.
+
+- **Complying with Security Standards**: Many organizations are required to follow strict security guidelines to comply with regulations like GDPR. Secure API authentication practices help meet these compliance requirements. Some of the security standards can be [Data Encryption at Rest](https://dev.to/documatic/data-encryption-securing-data-at-rest-and-in-transit-with-encryption-technologies-1lc2), [Data Encryption in Transit](https://dev.to/documatic/data-encryption-securing-data-at-rest-and-in-transit-with-encryption-technologies-1lc2), just to ensure data are secured in different manners.
+
+
+## Implementing Secure API Authentication
+
+1. **Avoid Sending Credentials in the Request Body**:
+   Credentials should never be sent in the body of a request (such as in a [POST](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST) request) because the datas may be logged in plain text by the server or any intermediaries. Instead, use HTTP headers, which are generally more secure and less likely to be logged.
+
+   **Example**:
+```bash
+   curl -X POST https://api.example.com/resource \
+   -H "Authorization: Bearer your_api_key_here" \
+   -H "Content-Type: application/json"
+```
+In the example above, the API key is passed securely in the Authorization header.
+
+2. **Do Not Use Basic Authentication (Username and Password)** : Basic authentication sends the username and password encoded in base64, which is easily decoded if intercepted. Even if transmitted over HTTPS, basic authentication is not recommended for APIs. Instead, use more secure methods like API keys or OAuth tokens.
+
+3. **Use API Keys in Headers**: API keys should be sent in the request header, not in the request body or query parameters. Headers are typically not logged by servers or proxies, reducing the risk of sensitive data being exposed.
+
+4. **Rotate API Keys Regularly**: To enhance security, regularly rotate API keys and implement [rate limit](https://www.cloudflare.com/learning/bots/what-is-rate-limiting/). If an API key is compromised, the damage can be minimized by having short-lived keys and promptly revoking them.
+
+## Common Pitfalls of API Authentication
+
+- Avoid hardcoding API keys into your application code or storing them in publicly accessible repositories (e.g., GitHub). Instead, use environment variables or secure vaults to store sensitive keys.
+
+- Sending API keys in query parameters (e.g., ?api_key=your_key) can expose the key in logs, bookmarks, and browser history, making it vulnerable to leaks.
+
+- If you're using OAuth or token-based authentication, always validate tokens before allowing access to the API. Failing to do so can expose your API to unauthorized access.
+
+- Using long-lived tokens without expiration increases the risk of misuse if they are compromised. Instead, implement short-lived tokens and refresh mechanisms to ensure higher security.
+
+## Resources
+
+- [OAuth](https://auth0.com/intro-to-iam/what-is-oauth-2)
+- [Tokens](https://www.linkedin.com/posts/aransiolaayo_tokens-a-short-overview-tokens-are-like-activity-7252359472411545600-vr6k?utm_source=share&utm_medium=member_desktop)
+- [OWASP API Security Guidelines](https://owasp.org/www-project-api-security/)