This content has been marked as final. Show 5 replies
It is not recommended though: you can write a trigger in database for accounts table, where an account is inserted or updated or deleted - update globalusers set customPropety1 = "LastLogon_attribute_name in the table for accounts"
So.. the only way to put a value in the customeProperty field is when importing the user from OIM (or from a flatfile) ?
3 ways to update customproperty
1. OIM-OIA User import
2. Globaluser flat file import
3. Directly update the database as suggested above
Yes, as you have already configured environment to work for OIM and OIA integration.
1. Create a UDF in OIM and write a schedule task that stores the user password (Make it invisible)
2. Map the OIM's udf to update customProperty1 field.
3. Run "Import the users accounts and entitlements "
4. You should be able to see that the customProperty1 field is updated and then, trigger comes into action.
I would recommend using lastLogonTimestamp instead of lastLogon. The lastLogon is deprecated and is only valid for the server you are querying. Only lastLogonTimestamp is globally synchronized between all of the domain controllers in a domain.
Also please know that the 5 time values in Active Directory will return in 3 different formats. You may need to write a transformation class.