How to know when users were created in EEM

book

Article ID: 142078

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent CA Workload Automation AE

Issue/Introduction

How can we determine when a user was created in EEM?

Environment

Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)

Resolution

EEM can be configured such that users are either internal or external.

Internal means using EEM's internal user store, where you create users logins in EEM itself.
External means EEM is pointing to some LDAP such as Siteminder or Microsoft's Active Directory.


In the external configurations you do not create users in EEM.
You create users in your LDAP and EEM simply reads the LDAP.

If EEM is configured for external user store, then there is no reporting in EEM which will provide you details on when the id was created. You would consult your LDAP administrator to see what is available.


If EEM is configured for internal user store, and you create a new user you will see something logged in the audit.log

Example from my environment where I created a user named Frank:

/iTechPoz/Entities/Users/Frank
GlobalUser
EiamAdmin
798e45d2c38ae306ad624a96ae2a161c-5df789ac-f4240f80-252a
IAM.Admin.soInsert.S.I
13648
efcb36487826e4355ea5e6d4f6bc1f52-5df789ac-f4240f80-1
lvntest002921.bpc.broadcom.net
iPoz
Success
1576682452
Linux 2.6.32-754.14.2.el6.x86_64
Info

The above shows the user Frank was created on 12/18/2019.
Key fields to focus on
/iTechPoz/Entities/Users/Frank
GlobalUser
IAM.Admin.soInsert.S.I
1576682452

That date is in unix epoch format.
If you are familiar with AutoSys you can feed that value into time0 to get a more human friend time/date.
Example:
# time0 -a 1576682452
CAUAJM_I_50097 External Time: 12/18/2019 10:20:52

Be aware that the audit.log can/will rollover so it is not likely to have ALL your history.

Other methods to get the data would be to stop dxserver, export the EEM db via dxdumpdb, restart dxserver, then you can view the output file from your dxdumpdb.
Example:

$ dxserver stop all
Stopping all dxservers
....
itechpoz stopped
$ dxdumpdb -f /tmp/eemdump.out itechpoz

$ dxserver start all
Starting all dxservers
itechpoz starting
..
itechpoz started
$ vi /tmp/eemdump.out

--- excerpt from the eemdump.out file showing the Frank user ---

dn: cn=Frank,cn=Users,cn=Entities,cn=iTechPoz
objectClass: pozObject
cn: Frank
pozId: 3989bbeb9bad94ca27398f534cb9c744-5df789ac-f4240f80-2529
pozLink: cn=Frank, cn=Users, cn=Entities, cn=iTechPoz
pozClass: O_E_U
pzEnableDate: 0
pozLocation: /iTechPoz/Entities/Users
pzCreateTimestamp: 20191218152052
pzChangePasswordNextLogin: false
pzOverridePasswordPolicy: false
pzPasswordChangeDate: 1576682452
pozGeneration: 2
modifyTimestamp: 20191218152056.475Z
modifiersName: cn=PozAdmin,cn=Admins,cn=Entities,cn=iTechPoz
pzModifyTimestamp: 20191218152056
creatorsName: cn=PozAdmin,cn=Admins,cn=Entities,cn=iTechPoz
createTimestamp: 20191218152052.441Z
pzDisableDate: 0
userPassword: {SHA512}A+99S8TXV0/Jaag6lGWO5XpK9uc4+/ooBayxdbyaWOlVKS8v9b1mQd
i/iHnDInfuEwf9QsGzjvfCjJSzevMtQQ==
pzPasswordDigest: {SHA512}A+99S8TXV0/Jaag6lGWO5XpK9uc4+/ooBayxdbyaWOlVKS8v9b
1mQdi/iHnDInfuEwf9QsGzjvfCjJSzevMtQQ==
pzPasswordTimeToWarn: false
pzSuspended: false
pzSuspendedDate: 0
pzPasswordExpireTime: 0
pzUserName: Frank
pzIncorrectLoginCount: 0

You can see the create stamp
pzCreateTimestamp: 20191218152052

The format is

YYYYMMDDHHMISS

2019 12 18 15:20:52
(the hour is expressed from GMT)