Steps to reproduce:
1. Rename security_sample_ldap.xml-example to mh_default_org.xml
2. Configure LDAP settings
3. Access login page, looks like scripts and css are broken. (see file)
The login page is broken, no css no info
Beautiful login page
Workaround (if any):
I included the next lines on line 20 right URL security directive.
<sec:http pattern="/lib/**" security="none" />
<sec:http pattern="/admin-ng/scripts/**" security="none" />
<sec:http pattern="/admin-ng/styles/**" security="none" />
but I dont know what are the collateral effects of this. I got this from original mh_default_org.xml so I gues must be ok.
Another thing that happened to me, maybe because I am a bit dumb and took me a ridiculous amount of time to realize was when removing the comment from line 384 and 394 then the line 387 and 389 has comments too and they are broken so they don't break the comment starting 384. I know you can't have nested comments on xml, but maybe it could be a solution to move notes on lines 387 and 389 above line 384. This last is more a suggestion, thought.
This is my first ticket, so I am sorry if I have broken some rules or law please point me to the right way to do it.
If my "solutions" are right I can make a pull request with the changes if that is ok.
I came across this issue too before reading this ticket. Solution was for me the same.
Ruben, is this fixed by your recent LDAP patches?
Er... Maybe... I can check tomorrow
I just checked and the file is currently up-to-date. Therefore I'm closing this issue.
However, it is fair to notice that keeping these "sample" files up to date is very prone to errors, because not everybody remembers they need to update these files alongside the mh_default_org.xml file, and even if they do, they may not have the time and/or capacity to check whether these changes work in these variants of the security file and whether they do break something.