-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to disable login #37
Comments
Could you explain a bit more your idea? |
Perhaps an environment variable (e.g.,
This would allow a public-facing Gigwa instance to be less vulnerable to hacking attempts, meet organization security policy requirements, etc. |
My understanding is that you're talking about cases where all DBs would be public and no-one except the administrator would need to log into the system, correct? If you're referring to adding an Apache layer on top of Tomcat, I would rather avoid adding weight and complexity to the Docker image. I'm sure disabling the authentication system could be achieved by commenting out or amending a couple of lines in applicationContext-security.xml |
Thanks! I'm referring to the scenario where the If commenting-out lines in applicationContext-security.xml prevented user login, that would be the most-important first step towards a workable solution. Ultimately, it would be preferable to disable the login page completely (and remove the "Log-in" button from the navbar) to be more convincing for organization security personnel that the site is in compliance with such security policies--- and to avoid attracting hackers to even a non-functional login page. |
It would be helpful to have a configuration option to disable logins (e.g., to meet site security requirements).
The text was updated successfully, but these errors were encountered: