Renaming Application objects

Which IIQ version are you inquiring about?

8.4

Share all details about your problem, including any error messages you may have received.

I have a requirement to rename the application in the Production environment. In past I have used the IIQ console command rename to achieve this thing. However, from the SailPoint support team I got to know that this is not a right way to rename the application name :slightly_smiling_face:.

Anyone has any other solution to this problem?

Thanks!

Hi @zeel_sinojia,

you can use SSB and use a token for the name of application.

Hey, the applications are already live in PROD. Moving forward we will use token approach. Just checking for the older applications.

Hi @enistri_devo,

We have scenarios in which we have to rename the applications to match the name exact as is in the application inventory database. Hence, looking for the best approach to rename the applications.

Thanks,
Pallavi

I have found renaming an application to be problematic.

I recommend not even trying.

1 Like

Hi @paul_hilchey

would you be able to highlight the issues that you had faced with the application rename?

Also, we do not even have an option of specifying the displyName for an application.

Renaming application creates issue

  1. In the objects where the application name is referred instead of the application id (e.g. taskdefinition, AuditEvent etc)
  2. All the rules/scripts where we reference the application names.

Note: In case you tokenized the application name, and changing the name in the token may create a new set of objects for the application instead of renaming the existing one (this is my observation from the past).

Hi @ Zeel Sinojia,
The only approach available is renaming the application via the UI. However, before renaming, all references to the application such as in rules, workflows, and other configurations must be updated accordingly. If the application name is not referenced anywhere, it can be renamed directly.

1 Like

Hi Pallavi,

The worst problems we’ve had were with IdentityArchive objects (in the spt_identity_archive table).
If there are references to the old application name in there, then you will get null pointer exceptions seemingly at random.
There isn’t a good way to clean up the stale references.

Hi @paul_hilchey, Thank you for sharing this information. Curious to know what were the corrective actions performed to resolve the issues mentioned.

Some references that I am following: Renaming application name, with issue in identity.attributeAssignments.appicationName

Thanks,
Pallavi

Hi Pallavi,

Here is an sql query you can use to find stale references from the spt_identity_archive table:

select ia.name, ar.id, ar.name
from identityiq.spt_identity_archive ia
cross join xmltable('//Link/ApplicationRef/Reference'
                    passing sys.XMLType(substr(ia.archive,99))
                    columns
                       id varchar2(32) path '@id',
                       name varchar2(128) path '@name') ar
left join identityiq.spt_application a on a.id = ar.id
where a.id is null;

What to do when you’ve found stale references? The easy thing to do is delete the problem rows from the database, but you may miss some attribute changes that should trigger workflows

1 Like