Problem
Currently, any client in the network can connect to the server port and send print jobs without verification. This may cause unintended usage, abuse, or accidental overload.
Proposed Feature
Add a simple mechanism for client authentication, such as:
- IP allowlist (defined in config)
- or token-based check (client includes token in its request)
The server can verify incoming requests and reject those without valid credentials.
Benefits
- Prevents unauthorized use of the printer service
- Reduces risk of spam or accidental misuse in shared networks
- Keeps implementation lightweight and optional
This feature would be useful in environments where the server is shared between multiple teams or users.
Let me know your thoughts — I’d be happy to discuss or help implement it.