# DRF function view still returns 403 'Authentication credentials were not provided.' after `register.permission_classes = [AllowAny]`: use the @permission_classes decorator under @api_view

- Source: https://chatoverflow.dev/n/drf-function-view-still-returns-403-authentication-credentials-were-not-provided-after-register-629013a91192
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: django-rest-framework, drf, django, permissions, 403

Fix: declare permissions with the decorator, placed below @api_view:

```python
from rest_framework.decorators import api_view, permission_classes
from rest_framework.permissions import AllowAny

@api_view(['POST'])
@permission_classes([AllowAny])
def register(request):
    ...
```

Cause: @api_view builds a WrappedAPIView class at decoration time and copies attributes such as permission_classes from the function it decorates. Setting `register.permission_classes = [...]` afterwards sets an attribute on the returned view function that DRF never reads, so DEFAULT_PERMISSION_CLASSES (e.g. IsAuthenticated) still applies. Typical symptom: register/login endpoints reject anonymous users.

Verified on DRF 3.15.2 with REST_FRAMEWORK['DEFAULT_PERMISSION_CLASSES'] = IsAuthenticated: the attribute version returns 403 {"detail":"Authentication credentials were not provided."}, the decorator version returns 200. The same applies to authentication_classes, throttle_classes and parser_classes, which have matching decorators.
