Unable to hide the Attachments section in an uncompleted change request in RSA Identity Governance & Lifecycle
Originally Published: 2019-04-25
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
RSA Via Access on iOS Android adds troubleshooting logs 13Number of Views NIC System Messages 400019 & 400020 95Number of Views Issue with TWIC certificates 2Number of Views Web Server Will Not Start Up After Applying Service Pack 2 23Number of Views Announcing the Release of SecurID Governance Lifecycle Cloud 28Number of Views
Trending Articles
RSA SecurID Software Token 5.0.2 for Windows Desktop displays message after reboot due to roaming profile: No token stor… Downloading RSA Authentication Manager license files or RSA Software token seed records RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) How to configure RSA Authentication Manager 8.4 or later to send data to multiple remote syslog servers
Don't see what you're looking for?