-
New Feature
-
Resolution: Fixed
-
Major
-
Platform: All, OS: All
I already have apache and other security measure in place to secure hudson, but
need the TCP port for JNLP slave agent to be fixed for firewall issues.
I found the setting under security for this and if set manually in the
config.xml file it work with security not enabled, but if you make changes on
the configuration page it removes it if security is not enabled.
My suggestions would be
A. to move this setting to its own section to include any other JNLP settings.
B. Persist this setting regardless of the security setting if its already set.
Thanks
- is duplicated by
-
JENKINS-40228 Security config hides certain parts with 2.32
-
- Resolved
-
-
JENKINS-44382 "Configure Global Security" Does Not Save
-
- Resolved
-
-
JENKINS-12649 Need to activate Security to see options "TCP port for JNLP slave agents" and "Markup Formatter"
-
- Resolved
-
First of all, the port being under security was a bit unexpected on our end.
Having to enable security (we have it disabled) is very unintuitive and cost us time to figure out. That the JNLP port is bound no matter the enable security setting being turned on or off, is very questionable and confusing. This should defiitely be changed ASAP, to prevent user confusion. Especially, since simply moving the setting but keeping it as is should be rather simple!?
On one LTS installation, I have security enabled, but use anonymous access anyway. On a second installation, we use anonymous access with security disabled. The confusing part is that on the second installation, I can enable security to set the JNLP port, and then save the settings. Checking back, security is still disabled (I guess because no Security Realm was chosen) but the port is set. This is a very unintuitive and hidden behaviour.
This is assigned to @Kohsuke Kawaguchi, I guess since 2009. Is this something you can and will do? Or would it be helpful if someone from the community jumped in?