Change the PK field

Is your feature request related to a problem? Please describe. The PK on the APIKey model is the string containing the prefix and hash. This makes it challenging to work with when referencing it in URLs in many REST-based frameworks. eg. 2TothlA4.pbkdf2_sha256$36000$dfPh6LIy7NB3$FTA61Pvuq3gres5ZsclXimNCRz70jvDRl/ygYOjEiLc=. This contains a slash and other special chars that would typically be URL encoded.

Describe the solution you’d like Either convert the model to use a standard integer PK or provide some other means to reference it in such a way

Describe alternatives you’ve considered I’m not sure, but could this be handled through the solution being considered for #34?

[curtismorte]

@eagle-r, It’s a bad idea to pass an API Key in a URL. You’re essentially exposing your API Key.

With your reference to #34, that’s a solution. However, I think it’s actually a poor fix for the actual problem.

@florimondmanca, we need to normalize the table to have a generic based integer PK. With the completion of #34, those who need to change the PK to some other form of ID, say a UUID, will have the flexibility to do so.

[curtismorte]

@eagle-r and @florimondmanca, In my opinion, while this is technically not a bug and is more of a feature enhancement, the issue should be considered with the same level of priority as a bug.

Using a Model View Set requires a PK. The current PK we have is not a valid form of PK.