Bug 410861 - LDAP: Server field validation error appears in multiple LDAP fields
Summary: LDAP: Server field validation error appears in multiple LDAP fields
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: 3.1.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords: security
Depends on:
Blocks:
 
Reported: 2013-06-14 16:38 EDT by Latha Amujuri CLA
Modified: 2016-06-14 13:59 EDT (History)
5 users (show)

See Also:


Attachments
LDAP error message (96.70 KB, image/png)
2013-06-14 16:38 EDT, Latha Amujuri CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Latha Amujuri CLA 2013-06-14 16:38:24 EDT
Created attachment 232403 [details]
LDAP error message

- Manage Hudson
- Enable Security
- Select LDAP and click on the Advanced button
- Enter ldap://127.0.0.1 in the server field and tab out
Note no validation error is displayed
- Enter value in the Manager DN field and tab out
Now note that the error message 'Syntax of server field is SERVER or SERVER:PORT or ldaps://SERVER[:PORT]' appears below the Manager field
- Tab out of the Manager password field. 
Same error appears below the password field.

Screenshot with the error message below 3 fields is attached.
Comment 1 Denis Roy CLA 2013-11-08 08:59:51 EST
I've encountered this on bug 421277 comment 3.

Hudson is configured for LDAP and was working well.  

As an admin logged in, went to the Security Tab, and added a checkbox to one of the security settings, and nothing else.  Saved.  Afterwards, no one could log in.  hudson-security.xml now had (invalid) entries for Manager DN and Manager Password, even though I did not add them, or even expand the LDAP settings.

After clearing the invalid entries and restarting the instance all was well.  But all subsequent security changes require us to remember to go to the advanced LDAP settings and remove what Hudson is trying to add before saving.
Comment 2 Denis Roy CLA 2015-10-01 08:05:06 EDT
This happens to us on a regular basis.

What's worse is that the admin password (MINE) is stored in the hudson-security.xml file with either weak or no encryption.
Comment 3 Winston Prakash CLA 2015-10-01 12:47:45 EDT
Hi Latha, can you check if this happens in Hudson 3.3.0. As of 3.3.0, we moved to Spring security 3.x from 2.5.x
Comment 4 Denis Roy CLA 2016-02-02 16:06:25 EST
Still happens in 3.3.1.

See: 487043
Comment 5 David Williams CLA 2016-06-14 13:59:47 EDT
(In reply to Denis Roy from comment #4)
> Still happens in 3.3.1.
> 
> See: 487043

Add still on 3.3.2. See bug 495995. 

Quite a pain!