• State Suggested Answer
  • Replies replies
    40
  • Answers answer
    1
  • Subscribers subscribers
    21
  • Views views
    2284
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GMS 18.4.1 Build 951 Groupwise Group configuration - access control

Catia Rizzo

I'm building a new mobility server on SLES 15 SP4. 
I have it connected to a GroupWise Group, visiblity is system, and it loaded users. I also changed access control of people who can modify this group, and added administrators to give them this functionality, tested it etc, All seems to be working.

I then made some changes to this group in the GW admin console (ie access control - added users to people who can send to this group) and again only added administrators who are allowed to send to this group (so to prevent the entire organization from being able to send to this group..)

However, after I made this change and changed some notification settings on GMS, restarted GMS - the users disappeared.

I removed the users from access control - people who can send to this group - and restarted gms - and the users came back.

Is this as designed? We cannot change the access control of who can send to the group for mobility to read it?

  • 0 in reply to   

    i can confirm what catia had write. I had become the same information from mf-support.

    Build 931 is the latest, 928 is in the customer portal!

  • 0   in reply to   

    Hi.

    I just realized that this Issue was either not fixed, or it is back in the current GMS18.4.2 Builds 985 to 987.

  • 0 in reply to   

    We have not had any other reports of this being broken again in build 987.  Would you open a case on this so we can look into it?  Thanks, Pam

  • 0 in reply to 

    hi Pam, I've opened a case for this, slightly different than what's posted here, but still having issues with  groups added in mobility (not updating remove/adds from the group)   - also tested it with the new update as well 18.4.2 build 984 - same issue.

  • 0   in reply to 

    That's odd, cause I can dupe it on every GMS server I have. Make a GW group, add some users, and add access control to the group so that only certain users can send mail to it. Try to use that group as user source in GMS. You can add it, but absolutely nothing happens, no users will be added.
    OTOH, I don't think it's odd you don't get many reports of it, because I don't think many customers use the access control feature.

  • 0 in reply to   

    if you remove the access control does mobility re-sync all the users ?  Or does it just allow  the groups to update properly again?   Im concerned if I remove the access control it will remove the group from the production server and then I have to add the group back in  wait for accounts to sync again. 

  • 0 in reply to 

    I did see it come in this afternoon just before my shift ended, Catia.  Let me know if you have any problems with it.

  • 0 in reply to   

    Massimo - would you email me your duplication steps?  Thanks Pam

  • Suggested Answer

    0   in reply to 

    Yes, this is the defect that I found earlier in December and mentiomed to devs,within previous defect however, did not write extra defect / TID on this topic. So I did now. A workaround is to use a GAL user (only) which you defined in GMS configuration -> Configuration -> Device -> Address Book User. 

    portal.microfocus.com/.../KM000014030

  • 0 in reply to   

    My GMS address book user is the same user who is listed in the access control  for the group and it does not sync.. Is this what you mean for the workaround ? If so it doesn’t work. 

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.