Date: Fri, 29 Mar 2024 05:13:57 +0000 (UTC) Message-ID: <1563189738.7473.1711689237484@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7472_64616337.1711689237482" ------=_Part_7472_64616337.1711689237482 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
SURFnet looking for Grouper -> SCIM implementation.
SURFdesires:
Ultimately they are doing grouper -> apache syncope http://syncope.apache.org/
Would like us to provide a rich SCIM impl & let implementers handle = specific issues arising from it. SCIM Impl should handle both PUSH and PULL= .
SCIM ops coming out of Grouper:
want configurable incremental as well as bulk sync.
if SCIM endpoint is not available then do a periodic retry. AuthN will b= e by BASIC Auth, IP-based Auth, though nobody would complain if we supporte= d OAuth.
Would like to configure provisioning such that not all groups go to all = SPs. Rather, they would say this group X goes to SP Y and the SCIM provisio= ner would be smart enough to handle that and know not to put group X in SPs= (A,B,C).
They only want 1 stem pushed out via SCIM (other sems ignored).
Currently using Grouper version 1.6.3 =E2=80=93 SURFnet does NOT need th= is to work with 1.6.x branch and can live with it working only with current= .
normal group name coming out of grouper-SCIM