full text not editable in firefox/mozilla

[ardiederich]

I have a faq in 1.4.4 rc1 that isn't fully editable. I first noticed the issue in 1.4.3, but may have existed previously. The faq was probably enterd in 1.4.0 or 1.4.1. I have tested this with firefox 1.0, mozilla 1.7, IE 6 on xppro sp1, and a little with Konquorer and Opera 7.54.

What happens is I log into the admin side, edit the faq, and in the middle of item 10 the faq just stops. It displays all the text, properly formatted, until about halfway into the item. Then it just stops, about here:
10. The next field is for "Base context for this LDAP class". By default it is "cn=users,dc=<example>

This happens in firefox and mozilla. Also, those browsers report that the font is Heading 3. In IE the whole text appears, and it has the font as Normal. Konquorer and Opera don't show the neat html editor, so everything appears with the html formatting.

Here is the full text of my faq. Again, I'm using an itemized list for the numbering.

1. From the XCP Controller home, scroll down to the bottom under the Components section and add a new "Jabber Directory Suite." This will bring you to the Jabber Directory Suite Configuration page.

2. The first half of the JDS configuration page you can leave alone. Scroll down to the "XDB" section. You must now select the namespaces (ns) you want to access through JDS. Control-click all of the ns records except jcp:serverprefs. (So, select jabber:iq:auth, jabber:iq:register, http://www.jabber.com/schemas/cg.xsd, and http://www.jabber.com/schemas/jds.xsd, vcard-temp.)

3. Scroll down to the next section, "Hostnames for this Component." In the "Host Filters" text box enter "ldapsearch.<example>.<com>". This configures JDS to accept user search requests.

4. Scroll down again to the "JDS Config" section. You will need to edit both the "Add a Directory Server" and "Databases" sections. Start by clicking "Go" for "Add a Directory Server." This takes you to the "Directory server Configuration" page.

5. The Directory server Configuration page is where you configure how to connect to your AD server. Fill out your values for "Directory Server Hostname," "Directory Server Port," "Directory Server user," and "Password for directory service user." The server is probably your GC (Global Catalog) server, but could differ based on your setup of AD. Note: while the CG port works for auth, it does not work for Community Groups. The user is the DN of an administrator account or other account that has read access to the auth information in AD. Anonymous bind is not supported in XCP 3.1 or 4.0. After you have set all these values, click "Submit."

6. You should be back at the Jabber Directory Suite Configuration page. Scroll down to the bottom at the JDS Config > LDAP > Databases section, and click Go. This takes you to the "database Configuration" page.

7. Put a * in the "host:" field in the "Host Filters" section.

8. Click "Go" in the "Add a new Server" section. This brings up a short page where you add the server ID configured in step 5. If you left the defaults in step 5, the correct ID will be "server-1". Enter this and click "Submit".

9. You are now back on the database Configuration page. Here is where you will enter information specific to how your ADS is set up. The "LDAP object class to use for the Jabber ID" is probably going to be "User".

10. The next field is for "Base context for this LDAP class". By default it is "cn=users,dc=<example>,dc=<com>". Replace example and com based on your own AD setup.

11. The next field is "LDAP attribute to use for the Jabber display name". The common attribute to use is "displayName".

12. Next you have to define how JDS will build your JIDs. Under "Select exactly one of these options" choose "Static User JID". In "User Attribute" type "sAMAccountName". In "Host" type the hostname of your jabber server, such as "jabber.example.com".
13. Scroll down to the "JDS Command Definitions" section. Ensure Authentication Commands" is checked, then select "The authPlain command enables plain text authentication." You do not need to enter a lib.

14. Below that, check "The registerCheck command verifies that a user has an active, registered account" so JDS can validate jabber users. Again, you do not need to enter a lib.

15. Scroll down to "The ldapSearch command enables your users to search your LDAP". Check this box so Jabber users can search for other user accounts. (This is not the same thing as vcard information.) This is another section where you can add several lines by clicking "Go". Add what items you want on the next screen. The LDAP attributes in Active Directory for email, first name, and last name are "mail", "givenName", and "sn". The description you give them must not have any whitespaces.

16. You have now configured all of the JDS subcomponents. Click "Submit" on the "database Configuration" page, and then the Submit button on the "Jabber Directory Suite Configuration" page. If you see any errors, correct them and try again to Submit the new JDS component.

17. You are now at the main XCP Controller page and should see a new JDS component with a red "Stopped" banner next to it. Test to see if the JDS component will load by clicking the "Stop the System" link at the top of the page, and then clicking the "start the server now" link on the next page. You should now be back on the XCP Controller main page and see a green "Running" banner next to the JDS component. If it is Stopped, check syslog for errors.

18. Now that JDS is up and running you must configure the JSM plugin to use JDS. Click the Edit link in the "Jabber Session Manager" row to enter the "Jabber Session Manager Configuration" page.

19. Scroll down slightly to the "Optional modules" section. Check "mod_jds", uncheck "mod_auth_plain", "mod_auth_digest", and "mod_register". This enables JDS for authentication, and turns off the default authentication.

20. XCP 3.1 only: Scroll about halfway down to the "Agents" section. Select the "LDAP User Directory Agent" in the drop-down box and click Go.

21. XCP 3.1 only: Type in a description of the component (like "LDAP User Directory"). This description is what appears to the end-users, not what is displayed in the XCP Controller.

22. XCP 3.1 only: Under "Users may register info with the component" select "No". Click Submit to save the new Agent, and you will be brought back to the "Jabber Session Manager Configuration" page.
Further down the page past Agents you will see a "JDS Configuration" section. Check the box, then set both "Digest Configuration" and "Community Groups" to no.

23. Scroll down to "Registration Requirements". Since your users are already registered in AD you need to disable this. Uncheck the box.

24. JSM configuration is finished. Scroll to the bottom and click Submit.

25. On the XCP Controller main page, click the "Stop the Server" link.

26. Restart the server by clicking the "start the system now" link.

27. Test the new configuration by loggin into the XCP server with the Jabber Messenger client, specifying a username and password for a valid AD account. If the login fails check the JDS component configuration, syslog, and and LDAP logs for more detail.

[Thorsten]

Hi,

I will test this issue but maybe this is a browser bug.

bye
Thorsten