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

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?

Parents
  • +1  

    This was fixed in the last GMS builds. When there was a need to rebuild local GAL at GMS site, it was deleting and polling users into that GAL which lead into users were deleted from GMS. This polling does not happen anymore when GAL needs a rebuild.

    You will need same later build like 922 (402259-groupwise-mobility-service-18.4.1-x86_64-922.iso).

  • 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 

    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   

    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

Reply Children
  • 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. 

  • 0   in reply to 

    There must be the GAL user as only user listed. No one else.

  • 0 in reply to   

    I just tested this and it's still not syncing properly. This is my Access control user list for the group in GW:

    This is the GAL user on mobility:

    I restarted services on mobility, and those 8 failed users are still in the list, even though they are not in the Groupwise group.Am I doing something wrong?

  • 0 in reply to 

    please open a case on support portal and ask for the latest gms 18.4.2 build 987

    if the problem persist, open a case on support portal with this!

    cg

  • 0 in reply to 

    Claude - she has a case open already.

  • 0 in reply to 

    Thank you - i did see the update to the case with the 987 build, installed it - but same issue. Still seeing those users on mobility who are not in the groupwise group.

  • 0 in reply to 

    just another quick update -  engineering is working on this.

    I did some more testing, I've removed the access control list completely and it still doesn't sync properly on build 987. However, I did add a user and that synced. So for me it seems as if the issue is with account deletions.I tested this in my production server,  931 build,as well, the new account synced but the deleted accounts did not. The ACL is still in place with this group that's its configured to sync with.