Enhancements to Transaction WDR_ACF_WLIST 
By using the relevant Support Package there are two additional buttons that are available to transaction WDR_ACF_WLIST (see SAP Note 1731458).
Caution
Saving certificates using the browser deactivates an SAP security standard. Setting this switch is therefore at your own risk and assumes that all possible consequences have been considered.
Thsi setting is valid for all users application server-wide and is therefore usually made by administrators.
Click the Allow Cert. to be Saved Using Browser button in transaction WDR_ACF_WLIST.
In the next dialog box, click the Deactivate button.
This step deactivates the security standard and makes it possible to save certificates using the browser.
If the Web Dynpro application WD_ACF_DOWNLOAD_CERTIFCAT is started by either the users themselves or automatically as part of an application, it is now possible to save the certificate using the browser.
The save procedure is visible to the user and requires the user's explicit confirmation by clicking on the Save Certificate button of the related browser dialog. After being downloaded successfully, the local storage path of the certificate is displayed.
The current status of the option Allow Cert. to be Saved Using Browser is now constantly displayed in the browser dialog, that is, Saving Certificate is Allowed.
If you decide to reactivate the security standard, you must first repeat step 1. On the next dialog screen in step 2, select Activate. It is then no longer possible to save certificates using the browser, the status emessage in the browser shows a relevant text, and the Save Certificate button is no longer active.
Caution
Releasing client directories also deactivates an SAP security standard. Setting this switch is therefore at your own risk and assumes that all possible consequences have been considered.
By setting the All Client Directories switch, all available drives, network drives, and directories are released for writing and reading the files on the frontend computer. This means that existing client restrictions that were entered in the white list are ignored after release. The white list itself is still used as it can contain further entries (for example, addresses of the content server, starting of applications, and so on).
Note
Specified content servers are not affected by this change.