Skip navigation
4122 Views 10 Replies Latest reply: Feb 22, 2010 7:13 AM by selble RSS
selble Bronze 10 posts since
Feb 12, 2010
Currently Being Moderated

Feb 12, 2010 11:44 AM

Shared Roster Groups Between Two Domains

Hi all,

 

I'm currently piloting an Openfire installation, and one of our goals with this system is to deploy it in two different office locations, with two different domains, along with allowing users to chat between the two locations. In testing, I've been able to get this going without any problems. Except one.

 

In addition to allowing the users to be able to chat, we'd also like all users in both locations to see all users throughout the company. This is the problem. We're using an LDAP backend for our user groups (filtering on objectClass=posixGroup), and this works fine in each location, with memberUids simply being a user name. However, when we want to throw users from another domain in that system (i.e., memberUid: "fullusername@domain.com"), Openfire does not pick up that user name. I can put any name I want in as a memberUid for a group, and as long as it's a short user name (i.e., "fullusername"), they get added to the SRG, but as soon as I put a full user name in, it doesn't work.

 

When setting up Openfire without LDAP, I can add a full user name from a different domain to a SRG, which leads me to believe this should be a one or few line change in the source, but I thought it'd be best to ask if there's a legitimate reason for not doing this via LDAP, or if this could even be a bug.

 

If anyone has any ideas, that'd be appreciated. Thanks, in advance.

    • spulikon Bronze 14 posts since
      Oct 8, 2009
      Currently Being Moderated
      Feb 15, 2010 10:24 PM (in response to selble)
      Re: Shared Roster Groups Between Two Domains

      I think this has to do with the server setting "ldap.posixMode".

       

      -> If this is enabled, the groups' members are short user names in Active Directory. So openfire won't try to find the corresponding username again.

      -> If this is not enabled, the groups' members are Full DNs (instead of short user names). In this case, openfire tries to find the short username based on the Full DN (by extracting the user's CN part etc.).

       

      Is this setting enabled in your environment? If this is not enabled, could you try adding just short user names (instead of USER@DOMAIN) as members of Active directory groups? We just use single domain in our environment, so not really sure if that helps.

          • spulikon Bronze 14 posts since
            Oct 8, 2009
            Currently Being Moderated
            Feb 18, 2010 1:33 AM (in response to selble)
            Re: Shared Roster Groups Between Two Domains

            Is this what you are looking for: http://www.igniterealtime.org/issues/browse/ OF-162

              • spulikon Bronze 14 posts since
                Oct 8, 2009
                Currently Being Moderated
                Feb 18, 2010 7:01 PM (in response to selble)
                Re: Shared Roster Groups Between Two Domains

                I think now I understand your requirement correctly. As far as I know, IM b/w the users of different XMPP domains should be possible - which is actually working in your case. But, I am not sure whether it's possible to have users from different XMPP domains as part of shared roster groups. In short, I think developers may need to chime in.

                • pavel Bronze 2 posts since
                  Feb 19, 2010
                  Currently Being Moderated
                  Feb 20, 2010 7:13 AM (in response to spulikon)
                  Re: Shared Roster Groups Between Two Domains

                  Hello!

                  This works fine in ejabberd project  (http://www.ejabberd.im).

                  I have the same problem then migrate from ejabberd to openfire :-(

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points