I am also now seeing this error after bumping from 3.14.0 to 3.15.0. From Google, it appears this is coming from Django's command validation, not DRF specifically, but I believe it was introduced to DRF via this pull request, and it's unclear how to resolve the issue in DRF. The error suggests registering an admin model for "User", but I already have been, and doing so before registering the TokenAdmin:

I do extend the AdminSite:

class PlatformAdminSite(AdminSite):
    """
    Creates a base AdminSite. Models and URLs should be attached to an instance of this class.
    """
    site_header = settings.PROJECT_NAME + ' Administration'
    site_title = site_header
    index_title = settings.PROJECT_NAME

admin_site = PlatformAdminSite()

And register against that:

from django.contrib.auth import admin, get_user_model
from rest_framework.authtoken import admin as drf_admin
from rest_framework.authtoken.models import Token

class UserAdmin(admin.UserAdmin, BaseModelAdmin):
    # ... My extended UserAdmin code

class TokenAdmin(drf_admin.TokenAdmin):
    # ... My extended TokenAdmin code

# Then register the models to the admin
admin_site.register(get_user_model(), UserAdmin)
admin_site.register(Token, TokenAdmin)

It fails with this error. If I register directly against admin.site.register instead of my extended AdminSite, it works again. So what has changed with this release, and what do we need to change? Do we need to register something elsewhere, or has the way we need to extend AdminSite changed?

I noticed that you have a custom User model, right? So I think what happens is:

• Django register the default User model with the default admin
• DRF register the TokenProxy model with the default admin. But this model references your custom User model:

  django-rest-framework/rest_framework/authtoken/admin.py

  Line 11 in 337ba21

  User = get_user_model()

However, Django checks that the autocomplete_fields matches a model which is registered in the admin, but the user model registered in the default admin is the default one, not the custom one.

The simplest thing might be to revert the PR that caused it (I was waiting for this specific fix, but it doesn't work in all cases) and perhaps expand the documentation, which already explains how to patch the TokenAdmin. If folks want auto-complete fields, they can fix it in user land.

Agreed I think that PR should be reverted. DRF can either set TokenAdmin.autocomplete_fields as it does here, or call admin.site.register(TokenProxy, TokenAdmin), as it does here.

It can't do both, making this decision is too implementation-specific and thus won't work in all cases.

Created a PR to revert. For those looking to apply the same logic and enable auto-complete once the revert PR is merged, here is the code:

from rest_framework.authtoken.admin import TokenAdmin

TokenAdmin.autocomplete_fields = ("user",)

I've got the same issue, reverted back to 3.14.0.

temporary solution

added search_fields in my custom admin class

search_fields = ("USERNAME_FIELD",)