Subject: Grouper Users - Open Discussion List
- From: Andrew Jason Morgan <>
- To: "" <>, "Weston, Todd" <>
- Subject: Re: [grouper-users] Head Scratcher...
- Date: Sun, 20 Sep 2020 14:59:11 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oregonstate.edu; dmarc=pass action=none header.from=oregonstate.edu; dkim=pass header.d=oregonstate.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=r7R1QuF/Jpc+basNKjvgKrz31AZyqvNSMNYImjeRvJQ=; b=cq9ZMYVJAgAt1zQI6amrhU6fRx9RJcrLyIyGXHqLkljc3V3a33G9+gNROXZ7pLXHLCMNWfsubZa8NM6ehOhD4QMTBxqIV3AeZBSqNULDkX5CurMqZW6Xt3DF+0nQvKC3tr7LKaQaX3okQRgltoayc93hC0jKq0QOzkpDoseb2kXGlHPMSpx69/XyXok4+M4D7iJoHAQ1RZ2Y0CuDuxOSg5dW3CKCSoQp0b6RHmX0GjfcJXetq4fHXqJdgVbweijJIMozl2QI8AF3jV75pUeutBXXLZ5OppEA+dnApdRF1Dw0IVYma6/Rj0mYZIeS/1Fhz/o5WR745nIctl/JIH/afQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Xv4SFraLbGMq4ditzkADXTqXf79IO/PgfMEAjOaqWvBMuubuBLCQrUNg6auetub12U1rd4cXq99hJDyjLXHS7WV+ZS8nAbJcexkZuQ+AseZx/QMcLDtogv9OlTmcjUr08fX7d7OHfrNta6dU/BTnI5airU6YVyXkhydl38O8F5buq6W0ppXJy/eIkvYTUYORYj6A5h1lEuJqMm+djKyphCic3cuwOPmFMkiGp9cWzL6UtwaRNoQeVvHy6vXTQpDEzQxjc0X9LjS4HgLsNx9jmRV0hXHBoOHscpvX6KY2mUVAx62GpyeIvAMvlj+h4svhk2MPYLUhbLgYSZgDbR7KMg==
Sent: Saturday, September 19, 2020 6:07 PM
Subject: [grouper-users] Head Scratcher...
[This email originated from outside of OSU. Use caution with links and attachments.]
OK – this is one I cannot explain – any clues would be appreciated.
We are building our second instance of Grouper (Prod this time) and have used all GSH commands to build out the entire structure.
I added one of the seven provisioners to a test folder and made three groups which all provisioned in AD as expected. Only the “test:ad” folder below had the pspng attribute and value applied:
The other six provisioners defined were to be applied to the affiliates, employees and students folders in “wsu.edu:bundle:ad:campus.groups” and “wsu.edu:bundle:ad:role.groups” folder once the test groups were confirmed. All seven provisioners have a unique OU in the directory structure – naming in AD is similar to the folder structure in Grouper.
While only the one test provisioner was in place, I noticed that there were two classes of employee groups and two classes of student groups that had naming capitalization inconsistencies with our AD groups. I’m not sure if that would have been a problem, but I wanted to clean them up. So I made a list of the groups needing changes, ran a GSH script to remove them and regenerate them with the updated spelling version. All of our bundle groups are composites and no provisioning attributers had yet been applied to the folders. I didn’t even think to worry. The groups I deleted (which were empty and not provisioning) via GSH caused their counterparts in AD to delete – a behavior I would expect if provisioning were in place. We were able to restore the groups via the AD recycle bin, but the result was that thousands of employees and students lost critical group memberships – but wouldn’t realize until the following day when their Kerberos and SAML tickets expired.
Does anyone have any idea about how this would have occurred? I’ve triple checked the folders and the groups for provisioner attributes and there are none. I’m wondering if there is more juice in GSH to look at grouper-loader properties and find groups being removed via shell? Totally scratching my head over this. I’m fairly certain I won’t do anything to cause a repeat, but the circumstances seem fishy.
Information Security Analyst, Identity |
Information Technology Services | Washington State University
Phone 509.335.4479 PO Box 641222 Pullman, WA 99164-1222
- [grouper-users] Head Scratcher..., Weston, Todd, 09/20/2020
Archive powered by MHonArc 2.6.19.