com.atlassian.jira.bc.user.UserService |
Known Indirect Subclasses |
Clients of @PublicApi
can expect
that programs compiled against a given version will remain binary compatible with later versions of the
@PublicApi
as per each product's API policy as long as the client does not implement/extend
@PublicApi
interfaces or classes (refer to each product's API policy for the exact
guarantee---usually binary compatibility is guaranteed at least across minor versions).
@PublicApi
interfaces and classes are not designed to be implemented or extended by clients,
we may perform certain types of binary-incompatible changes to these classes and interfaces, but these will not
affect well-behaved clients that do not extend/implement these types (in general, only classes and interfaces
annotated with @PublicSpi
are safe to extend/implement).
UserService provides User manipulation methods exposed for remote API and actions.
Nested Classes | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
UserService.CreateUserValidationResult | |||||||||||
UserService.CreateUsernameValidationResult | |||||||||||
UserService.DeleteUserValidationResult | |||||||||||
UserService.FieldName | |||||||||||
UserService.UpdateUserValidationResult |
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Given a valid validation result, this will create the user using the details provided in the validation result.
| |||||||||||
Given a valid validation result, this will create the user using the details provided in the validation result.
| |||||||||||
Given a valid validation result, this will create the user using the details provided in the validation result.
| |||||||||||
Given a valid validation result, this will remove the user and removes the user from all the groups.
| |||||||||||
This method is deprecated.
Use
removeUser(ApplicationUser, DeleteUserValidationResult) instead. Since v6.0.
| |||||||||||
Execute the update using the validation result from
validateUpdateUser(User) . | |||||||||||
Validates creating a user for the admin section.
| |||||||||||
Validates creating a user for the admin section.
| |||||||||||
Validates creating a user for RPC calls.
| |||||||||||
Validates creating a user during setup of JIRA.
| |||||||||||
Validates creating a user during public signup.
| |||||||||||
This method is deprecated.
Use
validateCreateUserForSignup(com.atlassian.crowd.embedded.api.User, String, String, String, String, String) or
validateCreateUserForSetup(com.atlassian.crowd.embedded.api.User, String, String, String, String, String) instead. Since v5.0.
| |||||||||||
Validates the username for a new user.
| |||||||||||
Validates the username for a new user.
| |||||||||||
This method is deprecated.
Use
validateDeleteUser(ApplicationUser, String) or
validateDeleteUser(ApplicationUser, ApplicationUser) instead. Since v6.0.
| |||||||||||
Validates removing a user for the admin section.
| |||||||||||
Validates removing a user for the admin section.
| |||||||||||
Validates updating a user's details.
| |||||||||||
This method is deprecated.
Use
validateUpdateUser(com.atlassian.jira.user.ApplicationUser) instead. Since v6.0.
|
Given a valid validation result, this will create the user using the details provided in the validation result. Email notification will be send to created user - via UserEventType.USER_SIGNUP event.
result | The validation result |
---|
CreateException | if the user could not be created, eg username already exists |
---|---|
PermissionException | If you cannot create users in this directory (it is read-only). |
Given a valid validation result, this will create the user using the details provided in the validation result. No email notification will be send to created user.
result | The validation result |
---|
CreateException | if the user could not be created, eg username already exists |
---|---|
PermissionException | If you cannot create users in this directory (it is read-only). |
Given a valid validation result, this will create the user using the details provided in the validation result. Email notification will be send to created user - via UserEventType.USER_CREATED event.
result | The validation result |
---|
CreateException | if the user could not be created, eg username already exists |
---|---|
PermissionException | If you cannot create users in this directory (it is read-only). |
Given a valid validation result, this will remove the user and removes the user from all the groups. All components lead by user will have lead cleared.
loggedInUser | the user performing operation |
---|---|
result | The validation result |
This method is deprecated.
Use removeUser(ApplicationUser, DeleteUserValidationResult)
instead. Since v6.0.
Given a valid validation result, this will remove the user and removes the user from all the groups. All components lead by user will have lead cleared.
loggedInUser | the user performing operation |
---|---|
result | The validation result |
Execute the update using the validation result from validateUpdateUser(User)
.
updateUserValidationResult | Result from the validation, which also contains all the user's details. |
---|
IllegalStateException | if the validation result contains any errors. |
---|
Validates creating a user for the admin section. This method checks that external user management is disabled and that the user performing the operation has global admin rights. It also validates that all parameters (username, email, fullname) except for the password have been provided. Email is also checked to ensure that it is a valid email address. The username is required to be lowercase characters only and unique. The confirmPassword has to match the password provided.
This method allows the caller to name a directory to create the user in and the directoryId must be valid and represent a Directory with "create user" permission. This validation differs from the 'ForSetup' and 'ForAdminPasswordRequired' validations as follows:loggedInUser | The remote user trying to add a new user |
---|---|
username | The username of the new user. Needs to be lowercase and unique. |
password | The password for the new user. |
confirmPassword | The password confirmation. Needs to match password. |
The email for the new user. Needs to be a valid email address. | |
fullname | The full name for the new user |
directoryId | The User Directory |
Validates creating a user for the admin section. This method checks that external user management is disabled and that the user performing the operation has global admin rights. It also validates that all parameters (username, email, fullname) except for the password have been provided. Email is also checked to ensure that it is a valid email address. The username is required to be lowercase characters only and unique. The confirmPassword has to match the password provided.
This validation differs from the 'ForSetup' and 'ForAdminPasswordRequired' validations as follows:loggedInUser | The remote user trying to add a new user |
---|---|
username | The username of the new user. Needs to be lowercase and unique. |
password | The password for the new user. |
confirmPassword | The password confirmation. Needs to match password. |
The email for the new user. Needs to be a valid email address. | |
fullname | The full name for the new user |
Validates creating a user for RPC calls. This method checks that external user management is disabled and that the user performing the operation has global admin rights. It also validates that all parameters (username, email, fullname, password) have been provided. Email is also checked to ensure that it is a valid email address. The username is required to be lowercase characters only and unique. The confirmPassword has to match the password provided.
This validation differs from the 'ForSetup' and 'ForAdmin' validations as follows:loggedInUser | The remote user trying to add a new user |
---|---|
username | The username of the new user. Needs to be lowercase and unique. |
password | The password for the new user. |
confirmPassword | The password confirmation. Needs to match password. |
The email for the new user. Needs to be a valid email address. | |
fullname | The full name for the new user |
Validates creating a user during setup of JIRA. This method does not check for a writable User Directory because the embedded crowd subsystem will not be initialised, and we know we will just have an Internal Directory during Setup. It also validates that all parameters (username, email, fullname, password) have been provided. Email is also checked to ensure that it is a valid email address. The username is required to be lowercase characters only and unique. The confirmPassword has to match the password provided.
This validation differs from the 'ForAdminPasswordRequired' and 'ForAdmin' validations as follows:loggedInUser | The remote user trying to add a new user |
---|---|
username | The username of the new user. Needs to be lowercase and unique. |
password | The password for the new user. |
confirmPassword | The password confirmation. Needs to match password. |
The email for the new user. Needs to be a valid email address. | |
fullname | The full name for the new user |
Validates creating a user during public signup. This method checks that there is a writable User Directory available. It also validates that all parameters (username, email, fullname, password) have been provided. Email is also checked to ensure that it is a valid email address. The username is required to be lowercase characters only and unique. The confirmPassword has to match the password provided.
This validation differs from the 'ForAdminPasswordRequired' and 'ForAdmin' validations as follows:loggedInUser | The remote user trying to add a new user |
---|---|
username | The username of the new user. Needs to be lowercase and unique. |
password | The password for the new user. |
confirmPassword | The password confirmation. Needs to match password. |
The email for the new user. Needs to be a valid email address. | |
fullname | The full name for the new user |
This method is deprecated.
Use validateCreateUserForSignup(com.atlassian.crowd.embedded.api.User, String, String, String, String, String)
or
validateCreateUserForSetup(com.atlassian.crowd.embedded.api.User, String, String, String, String, String)
instead. Since v5.0.
Validates creating a user during setup of JIRA or during public signup. This method checks that there is a writable User Directory available. It also validates that all parameters (username, email, fullname, password) have been provided. Email is also checked to ensure that it is a valid email address. The username is required to be lowercase characters only and unique. The confirmPassword has to match the password provided.
This validation differs from the 'ForAdminPasswordRequired' and 'ForAdmin' validations as follows:user | The remote user trying to add a new user |
---|---|
username | The username of the new user. Needs to be lowercase and unique. |
password | The password for the new user. |
confirmPassword | The password confirmation. Needs to match password. |
The email for the new user. Needs to be a valid email address. | |
fullname | The full name for the new user |
Validates the username for a new user. The username is required to be lowercase characters only and unique across all directories.
loggedInUser | The remote user trying to add a new user |
---|---|
username | The username of the new user. Needs to be lowercase and unique. |
Validates the username for a new user. The username is required to be lowercase characters only and unique in the given directory.
loggedInUser | The remote user trying to add a new user |
---|---|
username | The username of the new user. Needs to be lowercase and unique. |
directoryId | The directory which the new user is intended to be created in. |
This method is deprecated.
Use validateDeleteUser(ApplicationUser, String)
or
validateDeleteUser(ApplicationUser, ApplicationUser)
instead. Since v6.0.
Validates removing a user for the admin section. This method checks that external user management is disabled and that the user performing the operation has global admin rights. It also validates that username have been provided.
SeevalidateDeleteUser(ApplicationUser, ApplicationUser)
for restrictions.loggedInUser | The remote user trying to remove a user |
---|---|
username | The username of the user to remove. Needs to be valid |
Validates removing a user for the admin section. This method checks that external user management is disabled and that the user performing the operation has global admin rights. It also validates that username have been provided.
SeevalidateDeleteUser(ApplicationUser, ApplicationUser)
for restrictions.loggedInUser | The remote user trying to remove a user |
---|---|
username | The username of the user to remove. Needs to be valid |
Validates removing a user for the admin section. This method checks that external user management is disabled and that the user performing the operation has global admin rights. It also validates that username have been provided.
Removing the user is not allowed if:PreDeleteUserErrors
rejects the requestloggedInUser | The remote user trying to remove a user |
---|---|
userForDelete | The user to remove. Needs to be valid |
Validates updating a user's details.
user | The user details to update |
---|
This method is deprecated.
Use validateUpdateUser(com.atlassian.jira.user.ApplicationUser)
instead. Since v6.0.
Validates updating a user's details.
user | The user details to update |
---|