It would be useful to support optional HTTP Basic Authentication in the HAJK backend to provide simple password protection for an entire HAJK instance.
A common use case is when a site needs to be accessible to external consultants or stakeholders but should not be publicly available to anyone who discovers the URL. While this can already be solved using a reverse proxy such as Nginx, having built-in support in the HAJK backend would make deployment simpler and more portable.
Suggested implementation:
Optional configuration for username and password through environment variables in .env.
When enabled, all backend routes require valid Basic Authentication credentials.
Disabled by default to maintain current behavior.
Example:
BASIC_AUTH_ENABLED=true
BASIC_AUTH_USERNAME=myuser
BASIC_AUTH_PASSWORD=mypassword
This would provide a lightweight protection mechanism for temporary projects, draft plans, and review environments without requiring additional infrastructure configuration.
It would be useful to support optional HTTP Basic Authentication in the HAJK backend to provide simple password protection for an entire HAJK instance.
A common use case is when a site needs to be accessible to external consultants or stakeholders but should not be publicly available to anyone who discovers the URL. While this can already be solved using a reverse proxy such as Nginx, having built-in support in the HAJK backend would make deployment simpler and more portable.
Suggested implementation:
Optional configuration for username and password through environment variables in .env.
When enabled, all backend routes require valid Basic Authentication credentials.
Disabled by default to maintain current behavior.
Example:
This would provide a lightweight protection mechanism for temporary projects, draft plans, and review environments without requiring additional infrastructure configuration.