0 votes

Hello,
We have scripts that rely on "is inactive"condition to process.I noticed that when editing a user, the "Last Logon" value is the one in the attribute "Last-Logon-Timestamp".
But the value closer to the last user logon time is the one in the attribute "Last Logon".
it seems that "user is inactive" condition of Adaxes look at Last-Logon-Timestamp".
If true, it is an issue because there is a several days difference between both attributes.

is that correct?

Thanks.

by (1.1k points)

1 Answer

0 votes
by (274k points)
selected by
Best answer

Hello,

To check if a user is inactive the Last-Logon-Timestamp / Last Logon and Password Last Set properties are used. Unlike Last Logon, the Last-Logon-Timestamp property is replicated and that is why they can have different values. In case of the If is inactive <period> condition, it is checked whether the values of Last-Logon-Timestamp / Last Logon and Password Last Set are within the specified period. So there should be no issues using the condition to check whether a user is inactive.

Related questions

0 votes
1 answer

Hi team, I have a few questions about approval flows How can I send approval to individual user (stored in an custom attribute)? How can I do actions based on request is ... -&gt; set accountExpire +6 Months if denied -&gt; do nothing and account will expire

asked Mar 13 by wintec01 (1.2k points)
0 votes
1 answer

Hello, I'm using property pattern for few things, and i just noticed that all my property pattern are applied on user creation (i don't want it to) Is there a way to "disable" property pattern on user creation ?

asked May 6, 2016 by Alexandre (460 points)
0 votes
1 answer

I've noticed that sometimes when users are added to groups, the timestamp of the user object is not updated. If you execute LDAP queries against the modifytimestamp field, this creates ... (as seen in the web interface) (scroll to right to see entire image):

asked May 21, 2014 by BradG (950 points)
0 votes
0 answers

I have a report which is basically a query for specific set of users for which I want the last logon attribute (not the last logon timestamp). When I sort the same report ... fine. But the same report in Adaxes web portal the sort is not working the same way.

asked 2 days ago by Vish539 (330 points)
0 votes
1 answer

I am unsure how to deal with this because of how Adaxes treats one identity account as two different objects, an AD and AzureAD user account, and both has different last logon values. What is a good way to combine the data?

asked Apr 22 by Daniel (100 points)
3,383 questions
3,082 answers
7,832 comments
545,482 users