How to obtain the RSA Identity Governance & Lifecycle Application Last Modified Date, Creation Date and ID (Version)
Originally Published: 2018-01-29
Last Modified: 2022-06-20
Article Number
Applies To
RSA Product/Service Type: Enterprise Data Collector (EDC), Account Data Collector (ADC)
RSA Version/Condition: 6.9.1 and above
Issue
So if, for example, it needed to be determined which of the Applications were recently onboarded, it cannot be done from the UI. This is because only the Last Modified Date is available, when an Application may have been onboarded in an earlier Creation Date + ID number.
Further, the ID is a sequential number for each Version of the Application, so we can treat the ID as the Version. However, please note that the ID does not start at 1 for each Application.
Finally, the Creation Date and ID (Version) is kept to maintain consistency for accounts and entitlements that were collected before a modification is made.
Tasks
- RSA Identity Governance and Lifecycle 7.0.2 Public Database Schema Reference
- RSA Identity Governance and Lifecycle v7.0.1 Public Database Schema Reference
- RSA Via L&G 7.0 Public Database Schema Reference
- Identity Management & Governance 6.9.1 Public Database Schema Reference
Applications
Lists all applications defined in RSA Identity Governance and Lifecycle.SQL> DESC T_APPLICATIONS Name Null? Type ----------------------------------------- -------- ---------------------------- ID NOT NULL NUMBER CURRENT_VERSION_ID NOT NULL NUMBER NAME NOT NULL VARCHAR2(256) CREATED_BY NOT NULL NUMBER CREATION_DATE NOT NULL DATE ...
SQL> DESC T_APPLICATIONS_VERSIONS Name Null? Type ----------------------------------------- -------- ---------------------------- ID NOT NULL NUMBER APPLICATION_ID NOT NULL NUMBER NAME NOT NULL VARCHAR2(256) CREATED_BY NOT NULL NUMBER CREATION_DATE NOT NULL DATE ...
The Last Modified date shown in the UI is actually the CREATION_DATE column in the T_APPLICATIONS table, for the current version of the Application record.
Historical data for earlier versions of an Application record are stored in the T_APPLICATIONS_VERSIONS table.
Resolution
- Connect to the RSA Identity Governance & Lifecycle database as the AVUSER, then set the formatting for the query results:
# sqlplus avuser/<password> SQL> col NAME format A45 SQL> ALTER SESSION SET nls_date_format = 'DD/MM/YYYY HH24:MI:SS';
- To determine the current Applications and their (Version) ID, issue the following SQLcommand:
SQL> SELECT NAME, ID, CREATION_DATE FROM T_APPLICATIONS;
- To determine when an Application was actually created (the minimum Version ID), issue the following SQL command:
SQL> SELECT A1.NAME, A1.ID, A1.CREATION_DATE FROM T_APPLICATIONS_VERSIONS A1 WHERE A1.ID = (SELECT MIN(A2.ID) FROM T_APPLICATIONS_VERSIONS A2 WHERE A2.NAME = A1.NAME);
Related Articles
RSA Via Lifecycle and Governance - How to set up an environment to run WebServices with Turkish Characters 14Number of Views ORA-01652: Unable to extend temp segment by 128 in tablespace TEMP in RSA Identity Governance & Lifecycle 805Number of Views RSA Identity Governance and Lifecycle MigrationReports.zip fails to install Migration Reports with ORA-04063: package body… 152Number of Views Account Data Collectors (ADC) fail with ORA-00904: "RESOURCE_NAME": invalid identifier after upgrading RSA Identity Govern… 205Number of Views How to determine who has created an RSA Identity Governance and Lifecycle Account Data Collector (ADC) 55Number of Views
Trending Articles
How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows Unique constraint (AVUSER.PK_WP_USER_DATA) violated error while upgrading RSA Identity Governance & Lifecycle
Don't see what you're looking for?