GMS fails to find a distribution list or a group via GroupWise provisioning if visibility of group is set to None.

  • 7015794
  • 20-Oct-2014
  • 20-Oct-2014


Novell GroupWise 2014
Novell GroupWise Mobility Service 2.0


With GW2014 a recommended configuration settings for adding users and groups into a system is to set provisioning and authentication into GroupWise. It is due to a fact that with GW2014 we do not populate any GroupWise attributes into any Directory. When you would try to add a user via LDAP provisioning, the search will look for eDir users with this extra GroupWise attribute which then fails as there are none.
Now if you intend to control users within your GMS server via a GroupWise enabled eDir group or via GroupWise Distribution List, you will fail to find a group via GroupWise Provisioning if GroupWise visibility of the group or DList is limited to None. If the group Visibility is set to Post Office or System, then you are able to find the group and add to the system.


This is currently considered as Enhancement for GMS part.
A workaround is to work with eDir groups. So if you were using before GroupWise enabled eDir group, you do not need to do anything. If you were using GroupWise Distribution List, you will need to create a group in eDir and associate your GroupWise DList with this eDir group.
Next, when you in GMS webadmin try to add a group, click on LDAP option instead of default GroupWise. Using LDAP source instead of default selected GroupWise overcomes GroupWise Visibility limitation.
Shall you get the same failed to find problems also here, then it is probably due to a fact that you have not configured LDAP server in your GMS configuration. Go back to Configuration section, and click on User Source.
Here in this section temporarily change Provisioning  and also Authentication back into LDAP. This step reveals LDAP configuration section where you can now fill in with a correct LDAP server information and Base DN search.
Then save it and reverse User Source back to GroupWise.