grouper-users - RE: [grouper-users] stemAdmin vs stem privilege
Subject: Grouper Users - Open Discussion List
List archive
- From: "Black, Carey M." <>
- To: Julio Polo <>, Grouper-Users <>
- Subject: RE: [grouper-users] stemAdmin vs stem privilege
- Date: Sat, 9 May 2020 02:39:24 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=osu.edu; dmarc=pass action=none header.from=osu.edu; dkim=pass header.d=osu.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=CtWr/BmEhTn48QSX5BzsSNt+bJkp3bAKMpW7XEYFwjU=; b=f5/hfbR51y+dHD3PpDdR7sl2Eb2G2dVwahaLi3WiCQ7sJp6OJUajMNgPYVCFtBcaECQmGlahZdLLYEZ18qYQ+oiCDOuWDXcfuhWqn8S331/U5fxF1uLIgyAprGyXT+dSe/kXLtErujbleioEJUBsIRYRCjA8JYmpi8funE0iASIHRY3dpScpPb3rocti2ms8an0lm++/l/PruW6flf9K+pcXyNKLmPzd2UfkAGgqxFr2gvWd0oXkqNF5M3hwzJX9qGxCndq/2UGA9BwhbLIhtioJoIDNA5C7D53/6Shg/AuLF954nHBUl5a+d5taV2BLaakEqTc3LO3PhBPWPR6s0g==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ltoLuFfXAt1tJcHDNBwLUxAcQP7NrQ0ZkM2TleGe7JJQqZOy3zgyL1qcAf0bK/wIjYHbdRYU/N5WdL053FJWi57tAX6IUeesPExCokri3SKihVbiDfQeHXKlFIovdOajjT7lv9zcTZsgIGlcedv539wxAhhPkqEcW+O7NgjTOtcjawDUkoXcbitfBAcMbHRmndcatGy2d9sXqVZkagkxihwvwjt8/j2KGhO5HZZ/dsEj2fOFW9MVrjFMFJbhmKsVj0HYZgqhvZfSPLXgGbrDcS1F5FqbRcgX+masCU0U6woVXWQZlpO63XjRcJeubO3dzPk5uoz+EAPHBuEee5p8lQ==
Julio,
I have no idea if this will work or make anything better….
However, I am curious if you change the endpoint that you were calling in the WS call? Also it may or may not help.. but I try to hold to this page for “definitions in Grouper terms”: https://spaces.at.internet2.edu/display/Grouper/Glossary
-- Carey Matthew
From: <>
On Behalf Of Julio Polo
We're testing the WS for Grouper 2.5. Has the 'stem' naming privilege been changed to 'stemAdmin' after Grouper 2.2?
We noticed an unexpected response from the 2.5 WS. We would send 'stem' as the naming privilege to assign, but the WS returns 'stemAdmin' as what was actually set.
Shall we stop using 'stem' and use 'stemAdmin' instead?
Here are the relevant portions of the HTTP request and response:
<WsRestAssignGrouperPrivilegesRequest>
Here's a pretty-printed version of the XML we got back:
{
Thanks.
Julio Polo University of Hawaii
|
- [grouper-users] stemAdmin vs stem privilege, Julio Polo, 05/09/2020
- RE: [grouper-users] stemAdmin vs stem privilege, Black, Carey M., 05/09/2020
- Re: [grouper-users] stemAdmin vs stem privilege, Julio Polo, 05/09/2020
- RE: [grouper-users] stemAdmin vs stem privilege, Black, Carey M., 05/09/2020
- Re: [grouper-users] stemAdmin vs stem privilege, Julio Polo, 05/11/2020
- RE: [grouper-users] stemAdmin vs stem privilege, Hyzer, Chris, 05/14/2020
- Re: [grouper-users] stemAdmin vs stem privilege, Julio Polo, 05/11/2020
- RE: [grouper-users] stemAdmin vs stem privilege, Black, Carey M., 05/09/2020
- Re: [grouper-users] stemAdmin vs stem privilege, Julio Polo, 05/09/2020
- RE: [grouper-users] stemAdmin vs stem privilege, Black, Carey M., 05/09/2020
Archive powered by MHonArc 2.6.19.