Versions Compared

Old Version 21

changes.mady.by.user Scott Koranda

Saved on

compared with

New Version 22

changes.mady.by.user Scott Koranda

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Grouper web services (WS) deployed. The Grouper Provisioner invokes web service calls to provision to Grouper.

  • A Grouper user that can authenticate to Grouper WS using basic authentication (a login and password). The authenticated Grouper user should have the necessary Grouper privileges to create folders, groups, and memberships in the stem or folder assigned for the CO. A common deployment pattern is to use the GrouperSystem user. You can test access to the Grouper WS using the command line tool curl like this:

    Code Block
    curl --user login:password https://some.server.org/grouper-ws/servicesRest/json/v2_2_000/groups/aStem%3AaGroup/members

    That command will query for the members of the group aStem:aGroup. Unless that stem and group combination happens to exist in your Grouper deployment you should see JSON returned with GROUP_NOT_FOUND, but you should not see any authentication errors.

  • Access to the Grouper configuration files in order to configure a COmanage Registry database view(s) as a Grouper subject source(s).
  • Administrator access to the COmanage Registry database in order to create and then grant SQL SELECT privileges to a user that Grouper can use to query the Registry database view(s) supplying the Grouper subject source(s).

...