META-INF/MANIFEST.MF Manifest-Version: 1.0 Created-By: 1.6.0_07 (Sun Microsystems Inc.)...

      "index" : {
        "creation_date" : "1509021055837",
        "number_of_shards" : "5",
        "number_of_replicas" : "1",
        "uuid" : "34AXOK0ITy6U7fzGItZJsQ",
        "version" : {
          "created" : "6000051"
        },
        "provided_name" : "fess_config.related_content"
      }
    }
  }

      "index" : {
        "creation_date" : "1509021055516",
        "number_of_shards" : "5",
        "number_of_replicas" : "1",
        "uuid" : "Vn_Ry5JPRSet5M3Cg2D17w",
        "version" : {
          "created" : "6000051"
        },
        "provided_name" : "fess_config.path_mapping"
      }
    }
  }

* **`200`** and above are for "Successful" responses. These are the ones you would use the most.
    * `200` is the default status code, which means everything was "OK".
    * Another example would be `201`, "Created". It is commonly used after creating a new record in the database.
    * A special case is `204`, "No Content".  This response is used when there is no content to return to the client, and so the response must not have a body.

  }

  public static <E> TestSetGenerator<E> newInstance(TestSetGenerator<E> delegate) {
    return new ReserializingTestSetGenerator<>(delegate);
  }

  @Override
  public Set<E> create(Object... elements) {
    return (Set<E>) super.create(elements);
  }

          }
        },
        "creation_date" : "1509021052202",
        "number_of_shards" : "5",
        "number_of_replicas" : "1",
        "uuid" : "KVOz6G2oR1S8lU5BvNyQrg",
        "version" : {
          "created" : "6000051"
        },
        "provided_name" : "fess_config.elevate_word"
      }
    }
  }

      "Sid": ""
    }
  ]
}
EOF
```

Create new canned policy by name `userManager` using `userManager.json` policy file.

```
mc admin policy attach myminio userManager adminManageUser.json
```

Create a new admin user `admin1` on MinIO use `mc admin user`.

```
mc admin user add myminio admin1 admin123
```

Once the user is successfully created you can now apply the `userManage` policy for this user.

```

			</la:option>
			<la:option value="filename.desc">
				<la:message key="labels.search_result_sort_filename_desc" />
			</la:option>
			<la:option value="created.asc">
				<la:message key="labels.search_result_sort_created_asc" />
			</la:option>
			<la:option value="created.desc">
				<la:message key="labels.search_result_sort_created_desc" />
			</la:option>
			<la:option value="content_length.asc">

			</la:option>
			<la:option value="filename.desc">
				<la:message key="labels.search_result_sort_filename_desc" />
			</la:option>
			<la:option value="created.asc">
				<la:message key="labels.search_result_sort_created_asc" />
			</la:option>
			<la:option value="created.desc">
				<la:message key="labels.search_result_sort_created_desc" />
			</la:option>
			<la:option value="content_length.asc">

      "index" : {
        "creation_date" : "1509021058796",
        "number_of_shards" : "5",
        "number_of_replicas" : "1",
        "uuid" : "5EWS2-qMT2WwHG0yPrhP3Q",
        "version" : {
          "created" : "6000051"
        },
        "provided_name" : "fess_user.group"
      }
    }
  }