Ansicht
Dokumentation

rsec/securestorage/keyfile - Path to file with key for the secure storage

rsec/securestorage/keyfile - Path to file with key for the secure storage

CL_GUI_FRONTEND_SERVICES - Frontend Services   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book
------------------------------------------------------------------------
| Parameter : rsec/securestorage/keyfile |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Short Description : Path to the file with the global key for the |
| secure storage. |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Parameter Description : |
| ----------------------- |
| You can use this parameter to specify a file that contains the |
| global key for the secure storage. |
| |
| If no value is specified, a default key is used. This is enhanced |
| with system-dependent data and usually provides sufficient |
| protection. |
| |
| Due to the dangers associated with using your own key (see below), |
| you should only use this function is you require a greater than |
| normal degree of protection. |
| |
| |
| If a value is specified, this must be the path to a file that can |
| be accessed from the application server. This file must contain a |
| continuous sequence of 48 characters from the hexadecimal character |
| set (0-9, A-F) at the start of the file. |
| |
| You can use the report RSECKEYGEN to generate a suitable key from a |
| pass phrase. |
| |
| If you specify only a file name, the system looks for this file in |
| the run directory of the application server. |
| |
| The first time the key is changed from the default value (default |
| key is used) to another value, the entries encrypted with the |
| default key are automatically encrypted with the new key the next |
| time they are accessed. |
| |
| |
| If you change the global key again, entries that were created with |
| the old key can no longer be decrypted. This means that a migration |
| in transaction SECSTORE is required. |
| |
| For more information, see the notes in the documentation. |
| |
| CAUTION: Keep a copy of the key file in a secure location. If the |
| file were to be lost, access to the entries in the secure storage |
| that were saved with this key is no longer possible. This can have |
| severe consequences for the entire system. |
| |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Application Area: System |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Unit: File name |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Default value: empty |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Who is permitted to make changes: The customer |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Limitations for operating systems: |
| Note that file names are platform-dependent. You should therefore be |
| cautious about using the option to make the profile parameter the |
| same on all servers in heterogeneous landscapes. |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Limitations for Database Systems: None |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Other Parameters Affected or Dependent: |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Valid Input, Formats, Areas: |
| If you change the value, the system checks whether the value meets |
| the conditions listed under "Parameter Description". If this is not |
| the case, the system rejects the change. |
| In this case, you can find more information in the developer trace |
| for the current work process. |
------------------------------------------------------------------------

------------------------------------------------------------------------
| Short Description : Path to file with key for the secure storage
------------------------------------------------------------------------

------------------------------------------------------------------------
| Applications Area : System
------------------------------------------------------------------------

------------------------------------------------------------------------
| Parameter Type : F
------------------------------------------------------------------------

------------------------------------------------------------------------
| Changes allowed : X
------------------------------------------------------------------------

------------------------------------------------------------------------
| Valid for Operating System : *
------------------------------------------------------------------------

------------------------------------------------------------------------
| Dynamic switchable : X
------------------------------------------------------------------------

------------------------------------------------------------------------
| Same on all Servers :
------------------------------------------------------------------------


General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 7907 Date: 20240419 Time: 181557     sap01-206 ( 5 ms )