#3872·OctoPrint

[Request] User accounts that cannot be logged into, or per-API key permissions

Author: timur-tabiCreated Dec 8, 2020Updated Jan 21, 2026
Labelsrequest

I'd like to see one of the following implemented:

  1. User accounts can only be accessed via the API key, and cannot actually be logged into. This would eliminate the need to specify a password, because there's no way to log into the account with that userid. This would allow to you create users with specific limited permissions, and then the API keys for that user would be also be restricted to those permissions. This would let you create different API keys for each application that you use (e.g. slicers that can upload the gcode to Octoprint directly), and that application would be restricted to whatever permissions of the API key. We can do this today, but we have the side-effect that the user can also be logged into, which creates a security hole.

  2. Allow us to specify a subset of permissions on a per-API key basis. So when you create an API key under a user, you can specify the permissions of that API key, and any application using that key would be restricted to the API's permissions rather than the user's permissions.