Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# LAST_MODIFIED_TIME

## Section

STAFFPRO

## Initial Value

0

## Units

N/A

## Range

0 or 1

## Description

By default, when `LDAPCONF` performs a partial synchronization, it checks the LDAP `ModifyTimeStamp` attribute to determine whether an entry has been modified since the last update (and so needs to be downloaded to iProcess). However, some LDAP Admin applications modify this attribute when handling user logins and authentication, which means that `LDAPCONF` cannot use it in this way. You can therefore use the LDAP `lastModifiedTime` attribute instead, with LDAP servers that require it.

The `LAST_MODIFIED_TIME` parameter defines which LDAP attribute `LDAPCONF` should check when performing a partial synchronization:

| • | `0` means that LDAPCONF checks the LDAP `ModifyTimeStamp` attribute to determine whether an entry has been modified since the last update.

| • | `1` means that LDAPCONF checks the LDAP `lastModifiedTime` attribute to determine whether an entry has been modified since the last update.

Note: This parameter is not present by default. You must add it if required. If this parameter is not present, the system defaults to using the LDAP `ModifyTimeStamp` attribute (`0`).

## Tuning

N/A

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.