LDAP Import into Assets

[Matthias Brockmeier]

Hello,

we are running the following environment:

Jira Datacenter 9.12.16 & Jira Service Management Datacenter 5.12.16

In this environment we use an Asset-Object-Scheme in which an Importer is configured to import our Active Directory Objects (Users) as Asset Object into the Object Type "Employee".

This importer runs every night at 01:00 AM and creates every newly created AD-User as an Asset-Object. It is also configured as deleting the Asset Objects for Users which are not available in the Active Directory anymore.

The creation of the Asset Objects works fine and as intended but since a few weeks the deletion of the Objects stopped working, so everytime we delete an AD-User we have to manually delete it from the Asset Database.

I already tried to delete the Object type mapping and create a new one without success. I also deleted the whole Importer configuration and configured it from scratch. Also with no succuess.

I also checked if the "Synchronizing Account" has the permission to change objects on the Asset Database.

Here is what the Importer looks like:

Did anyone else occured the same problem?

I hope my description is clear.

Kind regards,

[Marc - Devoteam]

Hi @Matthias Brockmeier 

Are you sure the user objects are deleted in the AD or has there been a change in AD, that they are just set to inactive in the AD instead of being deleted?

Then they will not be removed from assets, as they are still there. You might need an extra attribute then on the user to differentiate if the user is active or inactive.

[Matthias Brockmeier]

@Marc - Devoteam 

Thanks for your reply.

Yeah, I am sure that the user objects in the AD are deleted. I can provide some more screenshots to clarify what works and what does not work:

1. I create a new AD Account:

2. I run the Importer manually (usually it runs automatically at 1:00 AM):

After that user Asset Object is created as intented:

3. I delete the AD Account:

4. I manually run the Importer again:

Normally the Importer should find 1 missing object in the Employee Object-Type-Mapping and delete the Object "John Doe" but it doesn't.

Kind regards,

Matthias

[Evan Zafir]

I apologize I don't have an answer for you but I do have a question as your post sparked interest. 

Would you mind sharing your use case for importing LDAP into Assets? How is this used for your business?

Kindly,

Evan

[Marc - Devoteam]

Hi @Matthias Brockmeier 

This should be stated in the mapping details.

When you define your import, you will have to set up an object type mapping. While doing so, you will be offered the option what you want to do with missing objects. If you select remove there, only objects present in your csv file will persist

See this article: https://support.atlassian.com/jira-service-management-cloud/docs/create-objects-from-data-using-object-type-mapping/ 

I suggest tp try it first on a test scheme or in sandbox.

[Beth Starr]

Check the import configuration.  If it is not removing the user then in the configuration it is probably set to ignore.