Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Assets Data Manager for Jira Service Management Cloud is currently rolling out in Open Beta and will be available to all Premium + Enterprise sites by end of October 2024.
Active Directory is a tool produced by Microsoft that is used for Systems Management.
Active Directory uses a PowerShell connection to bring data into Assets Data Manager.
This task requires Data Manager Adapters admin permissions to complete. See how permissions and roles work in Data Manager.
Follow this procedure to connect this tool to Assets Data Manager using the custom-built Adapter:
Gather all of the information listed in the Data Manager Fields section, such as the Name, Object class, Data Source Name, and Data Source Type.
Gather all of the information in the Active Directory Fields section - this may require consultation with your tool’s SME.
Select Create Job, then select the Windows Active Directory (AD) tile
Configure all of the required fields with the appropriate information.
Follow all of the steps listed in the Authentication and Authorization section to properly configure Authentication and Authorization.
Review the Fields Retrieved section.
Data will be brought in from the tool each time this job is run.
You will need to specify the following information from Assets Data Manager:
Name - the name of the Connection, visible as the job name in Adapters.
Object - the name of the Object Class you want to the data to be loaded into.
Data Source Name - the type of data being created; which is usually the tool name, e.g AD, Qualys etc. Note: This can be the same as Name.
Data Source Type - what type of data is the tool providing? For example, Assets, CMDB, user location and more.
You will need to specify the following information from Active Directory:
AD Data Source - the Data Source Type drop-down box allows the user to specify where the data should come from. Select from:
User
Computer
Sites & Services (subnets)
Enable Discovery Domains - if the “enable discovery domains” is checked, the data adapter searches the Active Directory Domain Services to identify user accounts and their associated attributes.
Target Domains - where the domains you want to connect are listed, separated by a comma ,.
Username - the username that has been granted Read Only access to Active Directory.
Password - the corresponding password for the Username used above.
Authentication and Authorization are handled by the Adapter using a PowerShell connection.
To run the PowerShell query, the Adapters Client uses Remote Server Administration Tools (RSAT). Therefore, you need an RSAT enabled server to for PowerShell call to work.
If the Domains listed under Target Domains have different username and password requirements, these need to be set-up as separate jobs.
For example: Active Directory connections in the production environment may have a different username and password requirements to Active Directory in non-production.
The Primary Key retrieved by Active Directory is distinguishedname.
The following fields are retrieved for the Users object type:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
FlatDomain
QualifiedDomain
distinguishedname
name
whenChanged
whenCreated
location
userAccountControl
description
accountExpires
cn
mail
sAMAccountName
lastLogonTimestamp
employeeID
employeeNumber
employeeType
department
departmentNumber
title
countryCode
co
st
l
street
streetaddress
postOfficeBox
company
postalAddress
physicalDeliveryOfficeName
postalCode
ipPhone
telephoneNumber
mobile
givenname
sn
initials
displayname
lastlogon
lastLogoff
ADTarget
The following fields are retrieved for the Computers object type:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
FlatDomain
QualifiedDomain
distinguishedname
name
whenChanged
whenCreated
location
OperatingSystem
OperatingSystemServicePack
OperatingSystemVersion
userAccountControl
description
accountExpires
lastLogoff
cn
sAMAccountName
lastLogonTimestamp
ADTarget
Was this helpful?