Provision or reset an existing member password
Generated from the checked-in source. Do not edit this reference by hand.
PUT /api/v1/operators/{operator}/password
Requires installation administration or an owner permitted to manage the target member’s scope. Admin and viewer roles cannot perform this operation. First provision omits expected_revision; resetting requires the previous returned revision. Changes revoke all previous sessions atomically and append metadata-only audit events. Hashes are never returned. Bodies are limited to 4096 bytes and all success/error responses are non-cacheable.
Operation: setMemberPassword.
Authentication
Section titled “Authentication”Use the credential and permission scope described above. Each object below is an alternative; schemes within one object are required together.
[ { "bearerAuth": [] }]HTTP request
Section titled “HTTP request”Set NIU_ORIGIN to your installation origin (without /v1). Replace path, query and header placeholders with the required values. Query examples use curl 7.87 or newer to encode values with --url-query. Use the credential scope described above; a bearer token must have the authority required by this operation.
curl --fail-with-body -X PUT "$NIU_ORIGIN/api/v1/operators/{operator}/password" \ -H "Authorization: Bearer $NIU_BEARER_TOKEN" \ -H 'Content-Type: application/json' \ --data @request.jsonParameters
Section titled “Parameters”operator
Section titled “operator”Location: path. Required.
{ "type": "string", "format": "uuid"}Origin
Section titled “Origin”Location: header. Optional.
{ "type": "string"}Request body
Section titled “Request body”application/json
Section titled “application/json”Required.
{ "type": "object", "additionalProperties": false, "required": [ "email", "password" ], "properties": { "email": { "type": "string", "maxLength": 254, "description": "Unique normalized ASCII email for this member identity." }, "password": { "type": "string", "minLength": 15, "maxLength": 1024, "description": "At most 1024 UTF-8 bytes; spaces and Unicode are preserved." }, "expected_revision": { "type": [ "integer", "null" ], "minimum": 1 } }}Responses
Section titled “Responses”HTTP 200
Section titled “HTTP 200”New credential revision; no password or hash is returned.
Response headers:
{ "Cache-Control": { "schema": { "type": "string", "const": "no-store" } }}Content type: application/json.
{ "type": "object", "additionalProperties": false, "required": [ "revision" ], "properties": { "revision": { "type": "integer", "minimum": 1 } }}HTTP 400
Section titled “HTTP 400”Invalid email, password bounds or JSON request.
HTTP 401
Section titled “HTTP 401”Missing, expired or revoked administrative session.
HTTP 403
Section titled “HTTP 403”Role or supplied Origin is not permitted.
HTTP 404
Section titled “HTTP 404”Member is outside the caller’s scope.
HTTP 409
Section titled “HTTP 409”Credential revision changed, member was revoked, or email is already assigned.
HTTP 429
Section titled “HTTP 429”Bounded password-worker capacity reached; Retry-After is 60 seconds.
HTTP 501
Section titled “HTTP 501”Password sign-in has not been configured.
HTTP 503
Section titled “HTTP 503”Durable storage or credential processing is unavailable.
Behavior and supported scope
Section titled “Behavior and supported scope”Requires installation administration or an owner permitted to manage the target member’s scope. Admin and viewer roles cannot perform this operation. First provision omits expected_revision; resetting requires the previous returned revision. Changes revoke all previous sessions atomically and append metadata-only audit events. Hashes are never returned. Bodies are limited to 4096 bytes and all success/error responses are non-cacheable.