Unable to hide the Attachments section in an uncompleted change request in RSA Identity Governance & Lifecycle
Originally Published: 2019-04-25
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.1.0, 7.1.1
Issue
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.1.0 P09
- RSA Identity Governance & Lifecycle 7.1.1 P03
- RSA Identity Governance & Lifecycle 7.2
The fix is to enable the Show Attachments Tab and the Add/Delete Attachments (found under Requests > Workflows > {workflow name} > Job Properties panel right-hand side > Request Settings section) functionality within the request workflow. The configuration of these buttons works as follows once the patch is applied:
Scenario 1
Configuration: These are the default workflow settings.
- Show Attachments Tab - checked
- Add/Delete Attachments – checked
Result:
The Attachments section is visible in an open change request.
Scenario 2
Configuration:
- Show Attachments Tab - unchecked
- Add/Delete Attachments – unchecked
Result:
The Attachments section is not visible in an open change request.
Scenario 3
Configuration:
- Show Attachments Tab - unchecked
- Add/Delete Attachments – checked
Results:
The Attachments section is visible in an open change request. Checking the Add/Delete Attachments option implicitly enables the Show Attachments Tab since you cannot add/delete an attachment without seeing the Attachments section.
Scenario 4
Configuration:
- Show Attachments Tab - checked
- Add/Delete Attachments – unchecked
Results:
The Attachments section is not visible in an open change request. Disabling the Add/Delete Attachments functionality implicitly disables the Show Attachments Tab functionality.
Workaround
A. Style sheet
- Create a style sheet called hide_attachments.css with the following contents:
#attachments_upload {
visibility" hidden;
}
- Upload this file into the RSA Identity Governance & Lifecycle User Interface (Admin > User Interface > Files).
B. Customerstring.properties
- Create a customerstring.properties file, or edit the existing customerstring.properties file if one already exists. Add the following content:
ATTACHMENTS=
Note the name of this file has to be customerstring.properties.
- Upload this file into the RSA Identity Governance & Lifecycle User Interface (Admin > User Interface > Files).
C. Attachment File Extensions
As an additional deterrent to uploading attachments should the Attachment section be accidentally exposed in the change requests again, restrict the allowed attachment file extensions by going to Requests > Configuration > Settings > Edit. Add an invalid file extension, as in the screenshot below:
Related Articles
Add a Risk-Based Authentication Policy 8Number of Views Log Artifacts generation fails due to ORA-31061 error in ASR report generation in RSA Identity Governance & Lifecycle 119Number of Views This request contains no changes. It cannot be submitted error when adding entitlement belonging to a role in RSA Identity… 24Number of Views RSA WebSerivce "Invalid column name" when creating a change request to terminate a user in RSA Governance & Lifecycle 15Number of Views Announcing the Release of SecurID Governance Lifecycle Cloud 32Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to test RSA Identity Router (IDR) Secure Connector connectivity to the RSA ID Plus Cloud Access Service RSA SecurID Software Token for Microsoft Windows shows blank screen when asked to select a device where the token will be … RSA Governance & Lifecycle Generic Database Collector Guide RSA Authentication Manager 8.7 SP2 Administrator's Guide
Don't see what you're looking for?