## Introduction
**Django REST Framework API Key is a powerful library for allowing server-side clients to safely use your API.** These clients are typically third-party backends and services (i.e. _machines_) which do not have a user account but still need to interact with your API in a secure way.
### Features
- βοΈ **Simple to use**: create, view and revoke API keys via the admin site, or use built-in helpers to create API keys programmatically.
- π **As secure as possible**: API keys are treated with the same level of care as user passwords. They are only visible at creation and hashed before storing in the database.
- π¨ **Customizable**: satisfy specific business requirements by building your own customized API key models, permission classes and admin panels.
### Should I use API keys?
There are important security aspects you need to consider before switching to an API key access control scheme. We've listed some of these in [Security caveats](security.md#caveats), including serving your API over HTTPS.
Besides, see [Why and when to use API keys](https://cloud.google.com/endpoints/docs/openapi/when-why-api-key#top_of_page) for hints on whether API keys can fit your use case.
API keys are ideal in the following situations:
- Blocking anonymous traffic.
- Implementing API key-based [throttling](https://www.django-rest-framework.org/api-guide/throttling/). (Note that Django REST Framework already has many built-in utilities for this use case.)
- Identifying usage patterns by logging request information along with the API key.
They can also present enough security for authorizing internal services, such as your API server and an internal frontend application.
!!! warning
Please note that this package is NOT meant for authentication. You should NOT use this package to identify individual users, either directly or indirectly.
If you need server-to-server authentication, you may want to consider OAuth instead. Libraries such as [django-oauth-toolkit](https://django-oauth-toolkit.readthedocs.io/en/latest/index.html) can help.
## Quickstart
Install with `pip`:
```bash
pip install "djangorestframework-api-key==3.*"
```
!!! important
It is highly recommended to **pin your dependency** to the latest major version (as depicted above), as breaking changes may and will happen between major releases.
Add the app to your `INSTALLED_APPS`:
```python
# settings.py
INSTALLED_APPS = [
# ...
"rest_framework",
"rest_framework_api_key",
]
```
Run the included migrations:
```bash
python manage.py migrate
```
To learn how to configure permissions and manage API keys, head to the [User Guide](guide.md).
djangorestframework-api-key-3.1.0/docs/security.md 0000664 0000000 0000000 00000004736 14773715213 0022273 0 ustar 00root root 0000000 0000000 # Security
## Implementation details
### Key generation scheme
An API key is composed of two items:
- A prefix `P`, which is a generated string of 8 characters.
- A secret key `SK`, which is a generated string of 32 characters.
The generated key that clients use to [make authorized requests](#making-authorized-requests) is `GK = P.SK`. It is treated with the same level of care as passwords:
- Only a hashed version is stored in the database. The hashing algorithm is sha512. [^1]
- The generated key is shown only once to the client upon API key creation.
[^1]: Older versions of this module used the same hashers as Django's [`PASSWORD_HASHERS`](https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-PASSWORD_HASHERS). These hashers come with a large performance penalty and while critical for passwords, they aren't needed for high-entropy, randomly generated keys like the ones created by this module. Keys stored using these slower hashers will be upgraded when used.
### Grant scheme
Access is granted if and only if all of the following is true:
1. The configured API key header is present and correctly formatted. [^3]
2. A usable API key with the prefix of the given key exists in the database. [^4]
3. The hash of the given key matches that of the API key.
[^3]: To customize this behavior, see [API key parsing](guide.md#api-key-parsing).
[^4]: Only unrevoked keys are usable by default, but this can be customized with a [custom manager](guide.md#managers).
## Caveats
[API keys β Security](https://nordicapis.com/why-api-keys-are-not-enough/): depending on your situation, you should probably not use API keys only to authorize your clients.
Besides, it is NOT recommended to use this package for authentication, i.e. retrieving user information from API keys.
Indeed, **using API keys shifts the responsibility of Information Security on your clients**. This induces risks, especially if obtaining an API key gives access to confidential information or write operations. For example, an attacker could impersonate clients if they let their API keys leak.
As a best practice, you should apply the _Principle of Least Privilege_: allow only those who require resources to access those specific resources. In other words: **if your client needs to access an endpoint, add API permissions on that endpoint only** instead of the whole API.
Besides, it is highly recommended to serve the API over **HTTPS** to ensure the confidentiality of API keys passed in requests.
Act responsibly!
djangorestframework-api-key-3.1.0/docs/upgrade/ 0000775 0000000 0000000 00000000000 14773715213 0021517 5 ustar 00root root 0000000 0000000 djangorestframework-api-key-3.1.0/docs/upgrade/1.0.md 0000664 0000000 0000000 00000002221 14773715213 0022334 0 ustar 00root root 0000000 0000000 # Upgrading to 1.0
## Introduction
**The 1.0 release is incompatible with 0.x**. It introduces a new and more transparent API key generation and validation scheme which allows to pass it in a single header, instead of two previously.
This document lists the steps necessary to upgrade from 0.x to 1.0.
## Steps
### 1. Backup existing API keys
Unfortunately, it is not possible to provide a migration that would preserve existing API keys. This is because the cryptographic generation and validation methods have changed fundamentally, which means that new keys cannot be inferred from existing ones.
As a result, **all existing API keys will be destroyed** during Step 1/ described below. You may want to backup the existing data so that you can regenerate keys notify clients once migration is complete.
### 2. Reset migrations
**This step will destroy existing API keys**. It is necessary for the new migrations to run correctly.
```bash
python manage.py migrate rest_framework_api_key zero
```
### 3. Upgrade
```bash
pip install "djangorestframework-api-key==1.0.*"
```
### 4. Run migrations
```bash
python manage.py migrate rest_framework_api_key
```
djangorestframework-api-key-3.1.0/docs/upgrade/1.4.md 0000664 0000000 0000000 00000002004 14773715213 0022337 0 ustar 00root root 0000000 0000000 # Upgrading to 1.4
## Introduction
The 1.4 release includes a migration that adds and populates the `prefix` and `hashed_key` fields to API keys.
This document lists the steps necessary to upgrade from 1.3.x to 1.4.
## Steps
### 1. Migrate the built-in API key model
The `APIKey` model can be migrated using the migration shipped with this package:
```bash
python manage.py migrate rest_framework_api_key
```
### 2. Migrate custom API key models (if applicable)
If you have a custom API key model deriving from `AbstractAPIKey`, you need to **manually add the migration** to your application.
- Copy the migration script below to your app's `migrations/` directory. Be sure to modify `APP_NAME`, `MODEL_NAME` and `DEPENDENCIES` as seems fit. You can name the migration script `xxxx_prefix_hashed_key.py` (replace `xxxx` with the next available migration ID).
```python
--8<-- "src/rest_framework_api_key/migrations/0004_prefix_hashed_key.py"
```
- Apply the migration:
```bash
python manage.py migrate 
