Authentication with DRF_API_KEY_SECRET_KEY_HEADER only

Is your feature request related to a problem? Please describe. It would be handy to allow client to use only a secret key value DRF_API_KEY_SECRET_KEY_HEADER to access endpoints.

Describe the solution you’d like Client software provides only DRF_API_KEY_SECRET_KEY_HEADER and has its access to the endpoints and it is clear on the Django side to which client this key belongs to.

Describe alternatives you’ve considered Adopt DRF token authentication for non-human clients.

[ssrebelious]

I suppose then, that the issue of having 2 separate credentials is only that of UX from your users perspective?

Yes, UX is better with a single key only, without any additional IDs. I do integrate your library and will have to use both ID and the key (as there are no other options at the moment), though I would like to implement desired behaviour in feture if this package will provide needed functionality.

I want access to my API to be as simple as this example from geocoder:

>>> import geocoder # pip install geocoder
>>> g = geocoder.bing('Mountain View, CA', key='<API KEY>')   # notice that only API-key is required
>>> g.json
...

[ssrebelious]

Great job! 👏