Openfire (ARCHIVED)

Subscriptions not working when baseDN has a comma that is not a delimiter (unenclosed string)

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.5.0
  • Fix Version/s: 3.6.0
  • Component/s: None
  • Labels:
    None
  • Environment:

    Active Directory

  • Acceptance Test - Add?:
    No
  • Acceptance Test - Entry:
    Hide

    1) setup Openfire in LDAP mode with Active Directory
    2) use a baseDN such as the one in the description
    3) enable contact list sharing for a group
    4) look at the roster for the members of that group. The subscriptions will all be "to". Presence in Spark will be messed up. The groups for a user will show as None

    Show
    1) setup Openfire in LDAP mode with Active Directory 2) use a baseDN such as the one in the description 3) enable contact list sharing for a group 4) look at the roster for the members of that group. The subscriptions will all be "to". Presence in Spark will be messed up. The groups for a user will show as None

Description

If you have a baseDN such as the following, rosters will be messed up (all subscriptions = to):

ou=Jive Software\, Inc,dc=support,dc=jive,dc=com

This also seems to affect the groups that a user belongs to. It will always show up as "None" when you look at the user summary. On the client-side, presence does not work properly.

Activity

Hide
Permalink
Austen Rustrum added a comment -

added generic system property "ldap.encloseDNs". Problem was caused by an unenclosed baseDN.

Show
Austen Rustrum added a comment - added generic system property "ldap.encloseDNs". Problem was caused by an unenclosed baseDN.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.