java.lang.Object | |
↳ | com.atlassian.jira.bc.user.MockUserService |
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Given a valid validation result, this will associate a user with an application by adding that user to all the
default groups assigned to that application (regardless of the license).
| |||||||||||
Create a new application user if the provided
isValid() . | |||||||||||
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.
| |||||||||||
Allows you to construct
ApplicationUser for validateUpdateUser(ApplicationUser)
| |||||||||||
Given a valid validation result, this will remove the user and removes the user from all the groups.
| |||||||||||
Given a valid validation result, this will disassociate a user from an application by removing that user from all
the groups assigned to that application.
| |||||||||||
Execute the update using the validation result from
validateUpdateUser(ApplicationUser) . | |||||||||||
Validates associating a user with an application.
| |||||||||||
Validates associating a user with an application.
| |||||||||||
Validate that a new user can be created.
| |||||||||||
Validates creating a user for the admin section.
| |||||||||||
Validates creating a user for the admin section.
| |||||||||||
Validates creating a user during setup of JIRA.
| |||||||||||
Validates creating a user during public signup.
| |||||||||||
Validates creating a user during setup of JIRA or during public signup.
| |||||||||||
Validates the username for a new user.
| |||||||||||
Validates the username for a new user.
| |||||||||||
Validates removing a user for the admin section.
| |||||||||||
Validates removing a user for the admin section.
| |||||||||||
Validates disassociating a user from an application.
| |||||||||||
Validates disassociating a user from an application.
| |||||||||||
Validates updating a user's details.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
![]() | |||||||||||
![]() |
Given a valid validation result, this will associate a user with an application by adding that user to all the default groups assigned to that application (regardless of the license).
If the user is already associated with the application but is not the member of all the default groups, that user will be added to the default groups which that user does not belong to yet.
If any of the default groups assigned to this application are also assigned to other application(s), the user will also be associated with those applications as well.
This method is not the exact opposite to removeUserFromApplication(UserService.RemoveUserFromApplicationValidationResult)
.
While this method only adds user to the default groups assigned to an application, removeUserFromApplication
method removes user from all the group assigned to an application.
result | the validation result |
---|
AddException | |
---|---|
PermissionException |
Create a new application user if the provided isValid()
. This is typically
called after performing validateCreateUser(CreateUserRequest)
and verifying that the isValid()
. If the request is not valid or validateCreateUser(CreateUserRequest)
was not called prior to this method an IllegalStateException
would get thrown.
result | create user validation result returned from validateCreateUser(CreateUserRequest) , this contains the user details and instructions used to create new
user. |
---|
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 |
---|
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 |
---|
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 |
---|
Allows you to construct ApplicationUser
for validateUpdateUser(ApplicationUser)
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 |
Given a valid validation result, this will disassociate a user from an application by removing that user from all the groups assigned to that application. This also validates if the directory where the user lives is not fully read-only.
If the group set assigned to this application is a superset of the group set assigned to other application(s), the user will also be disassociated with those applications as well.
This method is not the exact opposite to addUserToApplication(UserService.AddUserToApplicationValidationResult)
.
While this method removes user from all the group assigned to an application, addUserToApplication method
only adds user to the default groups assigned to an application
result | The validation result |
---|
Execute the update using the validation result from validateUpdateUser(ApplicationUser)
.
updateUserValidationResult | Result from the validation, which also contains all the user's details. |
---|
Validates associating a user with an application. This method checks if the logged in user has the permission to add user to application. It then checks if there is an application specified by the application key. It also checks if there are any default groups assigned to that application. It validates if there are any spaces in the application license as well. This also validates if the directory where the user lives is not fully read-only.
loggedInUser | The logged in user |
---|---|
user | the user to be associated with the application |
applicationKey | the key of the application |
Validates associating a user with an application. This method checks there is an application specified by the application key. It also checks if there are any default groups assigned to that application. It validates if there are any spaces in the application license as well. This also validates if the directory where the user lives is not fully read-only.
user | the user to be associated with the application |
---|---|
applicationKey | the key of the application |
Validate that a new user can be created.
The validation instructions are specified in the UserService.CreateUserRequest
.
Typical validations are:
createUser(CreateUserValidationResult)
should only be called when the validationResult.isValid().
Usage example:
final CreateUserRequest createUserRequest = CreateUserRequest.withUserDetails(currentApplicationUser,
username, password, email, displayName)
result = userService.validateCreateUser(createUserRequest);
if(result.isValid())
{
userService.createUser(createUserRequest);
}
This request indicates that the user should be created in the default user directory with access to the default
applications.
request | user creation request containing new user details and validation instructions. |
---|
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 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 |
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 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. |
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 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.
See validateDeleteUser(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 disassociating a user from an application. This method checks there is an application specified by the application key.
Method expects for loggedInUser to be available via getLoggedInUser()
.
user | the user to be disassociated with the application |
---|---|
applicationKey | the key of the application |
Validates disassociating a user from an application. This method checks there is an application specified by the application key.
loggedInUser | application user performing the application access removal |
---|---|
user | the user to be disassociated with the application |
applicationKey | the key of the application |
Validates updating a user's details.
user | The user details to update |
---|