Limit some actions to only authenticate via token #1531
Labels
A-accounts
C-enhancement ✨
Category: Adding new behavior or a change to the way an existing feature works
Currently, all authentication for all routes happens either via a cookie through the browser or via an authentication header from cargo that uses a token. However, actions like publishing a crate and possibly others should only ever happen through cargo-- so it seems like a good idea to me to only authenticate for those actions via an auth header containing a token.
This is probably pretty low priority though.
The text was updated successfully, but these errors were encountered: