- Working with synchronized data
- Presenting synchronized data
- Using synchronized data in workflow
- Using synchronized data in JQL
- Using synchronized data in Script Runner
- Using synchronized data in notification
Using synchronized data in workflow post function
Active Directory Attributes Sync app provides an additional post function named Update Data. This post function allows to update data in LDAP server.
- This post function works only with a save server connection. In order to establish it you will need to configure an SSL connection to your Microsoft Active Directory.
- For information on adding a post function to a workflow’s transition, see Adding a post function.
You can use the user picker custom field only with attributes that meet the contains user condition.
The following tables present actions available in this post function.
Create user in AD
When you create a user in AD using this post function, only the following attributes are synchronized:
- cn
- displayName
- userpassword
All other attributes must be updated manually in your AD.
Table: List of parameters for Create user in AD
| Parameter | Description |
|---|---|
| Custom field for username | Select custom field to use when loading the username. |
| Custom field for user full name | Select custom field to use when loading user’s full name. |
| Custom field for user email | Select custom field to use when loading user’s email address. |
| Custom field for password | Select custom field to use when loading user’s password. |
| Object classes for user | Enter the name of the class used for the LDAP user object. For more classes, separate them by comma (,). Default values: top, person, organizationalPerson, user. |
| User Base DN | Enter subtree to which user will be added. For example: cn=users,dc=example,dc=com. |
| User Attribute DN | Enter name of an attribute in Active Directory which is used to log in to Jira. For example: sAMAccountName or cn. Default value: cn. |
Add user to AD group
Table: List of parameters for Add user to AD group
| Parameter | Description |
|---|---|
| User | Select user who will be added to the Active Directory group. |
| Source value | Select the specific Active Directory group to which user will be added. |
| Type group name | It is visible if only Group name in Source value is selected. Type name of group which exists in Active Directory. |
Adding user from a custom field
There are three Jira fields that you can use to determine which user should be added to a group:
- Assignee
- Reporter
- Current user
If the user you’d like to add doesn’t match any of those, you can use a custom field.
Steps
To add a user from a custom field:
- Create a Text Field (single line) custom field.
Type in the word Username as the custom field’s name (or choose a different one that will be easy to find)
Add the post function Deviniti [Active Directory Attributes Sync] - Update Data > Add user to AD group to your project’s workflow.
Select the Username custom field from the drop-down list next to Affected user.
Type in the user’s AD username into the text field on the issue view.
Result
The selected user is added to the chosen AD group.
Update user’s attribute in AD
Table: List of parameters for Update user’s attribute in AD
| Parameter | Description |
|---|---|
| User | Select user. |
| Field | Select field with user’s attribute in Active Directory. |
| New value | Select field which contains new value for this attribute. |
| Type attribute value | It is visible if only Source value is selected in New value field. Type value which will update selected user’s attribute. |
Reset user password in AD
Table: List of parameters for Reset user password in AD
| Parameter | Description |
|---|---|
| User | Select user. |
| Get new password from | Select custom field which contains new password (type: text). |
(Un)lock user account in AD
Table: List of parameters for (Un)lock user account in AD
| Parameter | Description |
|---|---|
| Operation | Select to lock / unlock user. |
| User field | Select field / custom field which contains user. It can be also Text Field but it’s necessary to store userName. |
Remove user from AD group
Table: List of parameters for Remove user from AD group
| Parameter | Description |
|---|---|
| User | Select user who will be removed from Active Directory group. |
| Source value | Select the specific Active Directory group from which user will be removed. |
| Type group name | It is visible if only Group name in Source value is selected. Type name of group which exists in Active Directory. |
- To use actions Add user to AD group or Remove use from AD group, be sure that groups information is filled in connection section. For more, see Configuring connection settings.
- Before you start, log in as a user with the Jira Administrators global permission.
Adding post function
Steps
To add an Update Data post function:
- Go to the Post Functions tab.
- Click Add post function.
- Select Deviniti [Active Directory Attributes Sync] - Update Data post function.
- Click Add.
- Select Connection.
- Select Action.
- Set necessary parameters for selected action (see table above).
- Click Save.
Result
New Update Data post function is added.
Updating post function
Steps
To update an Update Data post function:
- Go to the Post Functions tab.
- Click Edit next to the Deviniti [Active Directory Attributes Sync] - Update Data post function.
- Edit parameters for the post function.
- Click Update.
Result
Selected post function is updated.
Removing post function
Steps
To remove a Copy Property post function:
- Go to the Post functions tab.
- Click Delete next to the Deviniti [Active Directory Attributes Sync] - Update Data post function. Result
Selected post function is removed.
Comment settings
The post function Update Data can also add comments to issues, every time a change is made to your AD. You decide whether the comments appear in the Customer Portal or only internally. If you wish, you can also turn this function off, so that no comments get generated.
You can set it up while adding the post function to a workflow. Choose one of these three options:
- Internal: A comment will only be added to the Jira issue, so if reporters use the Customer Portal they won’t be able to see the comments.
- Public: The comment will be visible in Jira but also in the Customer Portal, so the reporters will be able to track the progress of their request.
- Disabled: No comments will appear in the comments section - either in the Jira issue view or in the Customer Portal.
