Usermanagement

Examples

If the authorization information provided in the HTTP request headers is valid,
the response will be:

  200 OK
  {
    "message": null,
    "result": null
  }

otherwise it will be:

  401 Unauthorized
  {
    "message": null,
    "result": null
  }

Examples

GET /usermanagement/v1/users/ABC230000/145121

Response:
{
  "message": null,
  "result": [
    {
      "resourceRepositoryKey": 145121,
      "resourceName": "bridges2-rm.psc.xsede.org",
      "username": "user1",
      "comment": "updated by PSC"
    },
    {
      "resourceRepositoryKey": 145121,
      "resourceName": "bridges2-rm.psc.xsede.org",
      "username": "user2",
      "comment": "updated by PSC"
    }
  ]
}

POST /usermanagement/v1/users/ABC230000/145121

Request body:
{
  "comment": "updated by PSC",
  "users": [
    {
      "username": "user5"
    },
    {
      "username": "user6"
    },
    {
      "username": "user7"
    }
  ]
}

GET /usermanagement/v1/users/ABC230000/145121/user5

Response:
{
  "message": null,
  "result": {
    "resourceRepositoryKey": 145121,
    "resourceName": "bridges2-rm.psc.xsede.org",
    "username": "user5",
    "comment": "updated by PSC"
  }
}

POST /usermanagement/v1/users/ABC230000/145121/user5

Request body:
{
  "comment": "added by PSC"
}

DELETE /usermanagement/v1/users/ABC230000/145121/user5

Request body:
{
  "comment": "removed by PSC"
}

Params

Param name	Description
request_number required	request number Validations: Must be a String
resource_repository_key required	resource key from CIDeR Validations: Must be a Integer
username optional	Validations: Must be a String