Hello All -
Just wonder what is the best way to work with EXPIRATION_DATE attribute with v6.9.1 above.
It does not seem to be in the PV_Account tables as far as I can see. I can see it in the T_Av_Accounts table.
Andrew
Hello All -
Just wonder what is the best way to work with EXPIRATION_DATE attribute with v6.9.1 above.
It does not seem to be in the PV_Account tables as far as I can see. I can see it in the T_Av_Accounts table.
Andrew
I've checked on v7.0.1 P02 and it seems that the expiration_date exists in PV_ACCOUNT
(see screenshot below)
Looks like I'm going to have to upgrade... 7.0 does not have this in the view of the PV_ACCOUNT
SELECT CREATION_DATE, LAST_LOGIN_DATE, APPLICATION_ID, IS_SHARED, NAME, DELETION_DATE, IS_DISABLED, ORPHANED_DATE, ADC_ID, IS_LOCKED, ID, CAD1, CAI1, CAS1, CAS10, CAS11, CAS12, CAS13, CAS2, CAS3, CAS4, CAS5, CAS6, CAS7, CAS8, CAS9, CAS5 as "DEPARTMENT", CAS1 as "DESCRIPTION", CAS4 as "EMAIL_ADDRESS", CAS6 as "EMPLOYEE_NUMBER", CAS12 as "EMPLOYEE_STATUS", CAS9 as "EXTERNAL_ID", CAS2 as "FIRST_NAME", CAS7 as "JOB_TITLE", CAI1 as "LASTLOGONTIMESTAMP", CAS3 as "LAST_NAME", LAST_REVIEWED_DATE, CAS11 as "LOCATION", CAS10 as "MANAGER", CAD1 as "NOT_USED", CAS13 as "TYPE", CAS8 as "USER_ACCOUNT_CONTROL" FROM V_UNIQUE_ACCOUNTS WHERE DELETION_DATE IS NULL
Also - something to note - there is no OOB mapping for this attribute in AFX. If I create one it will be in conflict with its internal operations.... hmmmm :-/
Are you also able to confirm there is a mapping in AFX in 7.0.1 above ?? If not there should be.
What do you mean when you say "If I create one it will be in conflict with its internal operations...."?
Why there will be conflict?
I discovered that I've already got a "Expiry_Date" custom attribute and was wondering why there was no data populated from my AD account collections. Even tho it was mapped correctly.
When you run a test on the collector to see the sample, you can see "EXPIRATION_DATE" OOB internal attribute mapped as well as my own "Expiry_Date".
As I understand, you can not map one collected item to two attributes as a rule in the configuration of a collector.
if you read this article carefully 000031262 - IMG Custom Attribute mapped to the Active Directory accountExpires attribute is no longer collecting after applying 6.9.1 P03
"If a custom attribute is defined for this attribute it will conflict." hence my missing data...
The user experience does not show this attribute automatically mapped - like a greyed out field... in the collector configuration.
AND to add to confusion - in v7.0 this OOB "Expiration_Date" can not be mapped with AFX - it is just not there in the drop down list to pick.
Wonder if my glasses need cleaning, or this is an oversight, or is available in 7.1 and above
There is work in progress to make this attribute configurable in the collector
Thanks for confiming.
If any product engineering teams are reading this - perhaps any introduction of new attributes which are out-of-box need to be holisticly intergrated/deployed into production releases end-to-end to provide a complete close loop managment.
This seems incomplete and has lead to confusion and custom workflows.
There is work in progress to make this attribute configurable in the collector