---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# LDAP extraction

# LDAP extraction {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

An LDAP extraction process can be implemented to detect disabled users.
An extract from your LDAP source can filtered for disabled users using an active flag that
can be set for every record in the import to 'false'. Specify ('target.active=false') and
copy into the Script field directly on the Table Transform Map
record.

## Benefits

Benefits to this method include:

* Simple scripting
* Existing user records are not involved in processing
* Inactive users are not loaded into a temporary import table
* No performance impact
{#r_LDAPExtraction__ul_jdk_kpt_cq}

## Drawbacks

Drawbacks to this method include:

* An additional process is created
* The extract set must be placed in a location where your data source can access it
{#r_LDAPExtraction__ul_srg_sr5_cq}

## Alternative method

[LDAP refresh filters](https://servicenow-prod.fluidtopics.net/fv3ualXq3z3jg_PRTtX0zA "Filters on the LDAP refresh process can be used to specify processing that ignores inserts of disabled users.") use multiple import jobs to divide different types of user records, segregating records for separate processing.