• Approval
  • Customer
  • Customer Request
  • Customer Transition
  • Jira Service Management Application
  • Organization
  • Organization Service Desk
  • Portals
  • Queue
  • Queue Settings
  • Request Attachment
  • Request Type
  • Request Type Permissions
  • Service Desk
  • Service Desk Customer
  • application-properties
  • applicationrole
  • attachment
  • avatar
  • cluster
  • comment
  • component
  • configuration
  • customFieldOption
  • customFields
  • dashboard
  • email-templates
  • field
  • filter
  • group
  • groups
  • groupuserpicker
  • index
  • index-snapshot
  • issue
  • issueLinkType
  • issuesecurityschemes
  • issuetype
  • issuetypescheme
  • jql
  • licenseValidator
  • monitoring
  • mypermissions
  • mypreferences
  • myself
  • notificationscheme
  • password
  • permissions
  • permissionscheme
  • priority
  • priorityschemes
  • project
  • projectCategory
  • projects
  • projectvalidate
  • reindex
  • resolution
  • role
  • screens
  • securitylevel
  • serverInfo
  • session
  • settings
  • status
  • statuscategory
  • terminology
  • universal_avatar
  • upgrade
  • user
  • version
  • websudo
  • workflow
  • workflowscheme
  • worklog
  • Assets - AQL
  • Assets - Analytics
  • Assets - Archived Objects
  • Assets - Attachments
  • Assets - Comments
  • Assets - Icons
  • Assets - Index Configuration
  • Assets - Object
  • Assets - Object Archive
  • Assets - Object Attribute
  • Assets - Object Connected Tickets
  • Assets - Object Restore
  • Assets - Object Schema
  • Assets - Object Type
  • Assets - Object Type Attribute
  • Assets - Progress
  • Assets - QR Code
  • Assets - Status Types
Server
Jira Service Management / Reference / REST API

password

Postman Collection
OpenAPI
GET

Get current password policy requirements

Returns the list of requirements for the current password policy. For example, "The password must have at least 10 characters.", "The password must not be similar to the user's name or email address.", etc.

Request

Query parameters

hasOldPassword

boolean

Responses

Returns a JSON array of the user-facing messages.

application/json

string

GET/api/2/password/policy
1 2 3 4 curl --request GET \ --url 'http://{baseurl}/rest/api/2/password/policy' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json'
200Response
1 "<string>"
POST

Get reasons for password policy disallowance on user creation

Returns a list of statements explaining why the password policy would disallow a proposed password for a new user. You can use this method to test the password policy validation. This could be done prior to an action where a new user and related password are created, using methods like the ones in UserService. For example, you could use this to validate a password in a create user form in the user interface, as the user enters it. The username and new password must be not empty to perform the validation. Note, this method will help you validate against the policy only. It won't check any other validations that might be performed when creating a new user, e.g. checking whether a user with the same name already exists.

Request

Request bodyapplication/json

The intended parameters for the user that would be created. The username and new password must be specified. The old password should be specified for updates where the user would be required to enter it and omitted for those like a password reset or forced change by the administrator where the old password would not be known.

displayName

string

emailAddress

string

password

string

username

string

Responses

Returns a JSON array of the user-facing messages.

application/json

string

POST/api/2/password/policy/createUser
1 2 3 4 5 curl --request POST \ --url 'http://{baseurl}/rest/api/2/password/policy/createUser' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json'
200Response
1 "<string>"
POST

Get reasons for password policy disallowance on user password update

Returns a list of statements explaining why the password policy would disallow a proposed new password for a user with an existing password. You can use this method to test the password policy validation. This could be done prior to an action where the password is actually updated, using methods like ChangePassword or ResetPassword. For example, you could use this to validate a password in a change password form in the user interface, as the user enters it. The user must exist and the username and new password must be not empty, to perform the validation. Note, this method will help you validate against the policy only. It won't check any other validations that might be performed when submitting a password change/reset request, e.g. verifying whether the old password is valid.

Request

Request bodyapplication/json

The intended parameters for the update that would be performed. The username and new password must be specified. The old password should be specified for updates where the user would be required to enter it and omitted for those like a password reset or forced change by the administrator where the old password would not be known.

newPassword

string

oldPassword

string

username

string

Responses

Returns a JSON array of the user-facing messages. If no policy is set, then his will be an empty list.

application/json

string

POST/api/2/password/policy/updateUser
1 2 3 4 5 curl --request POST \ --url 'http://{baseurl}/rest/api/2/password/policy/updateUser' \ --user 'email@example.com:<api_token>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json'
200Response