-
Type:
Bug
-
Resolution: Completed
-
Priority:
Blocker
-
Affects Version/s: COmanage Registry 4.3.4 (Ruddy Rex MR4)
-
Component/s: Registry
The documentation at
https://spaces.at.internet2.edu/display/COmanage/CoProvisioningTarget+API
indicates that the action "provision" should be implemented.
When I use this input JSON
$ cat group_provision.json
|
{
|
"RequestType":"CoGroupProvisioning", |
"Version":"1.0", |
"Synchronous":true |
}
|
|
with this curl command
curl \
|
--verbose \
|
--user co_35.scott_test_01:REDACTED \
|
-H "Content-Type: application/json; charset=UTF-8" \
|
-d @group_provision.json \
|
https://registry-test.cilogon.org/registry/co_provisioning_targets/provision/34/cogroupid:3823
|
I receive back a 302 redirect to https://registry-test.cilogon.org/registry/users/login
I suspect the configuration of the routing is not correct and complete for this REST API call.