RSA File Security Manager (FSM)
Microsoft Windows Server 2003 SP1
The folder in this case is not in use. Data in one folder called c:|Private, and Test data in c:\test-private. Can not encrypt c:\Private folder.
In FSM 2.1.0.9, there is a known issue that Security Officer can not encrypt a folder containing ReadOnly files/folders and is addressed in v2.2 and higher. Contact RSA Customer Support for latest version 2.2 of FSM.
Alternative workaround:
- Encrypt an empty folder e.g. c:\private\test\
- Copy the files and folder from c:\private\accounts_public\ to the encrypted folder i.e. c:\private\test\
- Rename the source folder c:\private\accounts_public\ to desired name and rename the encrypted folder (c:\private\test\) to c:\private\accounts_public\.
- Refresh the Adapter Manager Console using Refresh button far right in the right pane.
- User can delete the renamed source folder (unencrypted) after confirming that all data is intact in encrypted folder c:\private\accounts_public\
Related Articles
'com.rsa.authmgr.admin.tokenmgt.ListTokensByPrincipalCommand execution' error when trying to assign a token on RSA Authent… Number of Views Error scheduling data purging after new installation of RSA Identity Governance & Lifecycle 7.1.0 GA Number of Views "Error creating the Create New Authentication Source" is thrown when trying to add or edit an Authentication Source in RSA… Number of Views Adding a new user attribute in a user profile in RSA Authentication Manager 8.x Number of Views Error 'Invalid X.509 certificate uploaded' when adding a new application Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Patch Updates How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Artifacts to gather in RSA Identity Governance & Lifecycle
