How To Fix SIPT154 - No access to PSE-file for SSF-applic. SAFTPT in system &1 on server &2

SAP Error Message - Details

• Message type: E = Error

• Message class: SIPT - SIPT: Digital Signature Portugal

• Message number: 154

• Message text: No access to PSE-file for SSF-applic. SAFTPT in system &1 on server &2

What causes this issue?

The system runs a cloud service that requests the SAFTPT SSF-application
to sign a document with a Portuguese digital signature.
The SAFTPT SSF-application is inconsistently configured to generate this
signature in this system.

System Response

The SAFTPT SSF-application requires a system with a specific configured
certified PSE-file and is legally not allowed to generate a digital
signature without it.

How to fix this error?

The Secure Storage and Forward (SSF) environment of the dedicated cloud
system must be correctly setup. This setup change must be completed by
the provider of the cloud service you use.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SIPT154 - No access to PSE-file for SSF-applic. SAFTPT in system &1 on server &2 ?

  The SAP error message SIPT154 indicates that there is no access to the PSE (Personal Security Environment) file for the SSF (Secure Store and Forward) application, specifically for the application SAFTPT in the specified system and server. This error typically arises in the context of secure communications or cryptographic operations within SAP systems.
  Cause:
  
  File Permissions: The user or process trying to access the PSE file may not have the necessary permissions to read or write to the file.
  File Location: The PSE file may not be located in the expected directory, or the path to the PSE file may be incorrect.
  Configuration Issues: There may be misconfigurations in the SSF settings or the PSE setup in the SAP system.
  Missing PSE File: The PSE file for the SSF application may not exist or may have been deleted or corrupted.
  
  Solution:
  
  
  Check File Permissions:
  
  Ensure that the user under which the SAP application server is running has the necessary permissions to access the PSE file. This includes read and write permissions.
  
  
  
  Verify PSE File Location:
  
  Check the configuration to ensure that the PSE file is located in the correct directory. The typical path for the PSE file is usually in the instance directory under sec/ (e.g., /usr/sap/<SID>/SYS/global/security/pse).
  
  
  
  Recreate the PSE File:
  
  If the PSE file is missing or corrupted, you may need to recreate it. This can be done using transaction STRUST in the SAP GUI:
  
  Go to transaction STRUST.
  Select the appropriate PSE (e.g., SSL, SSO, etc.).
  Use the option to create or regenerate the PSE.
  
  
  
  
  
  Check SSF Configuration:
  
  Ensure that the SSF settings are correctly configured in the SAP system. You can check this in transaction SSFC or SSFC_ADMIN.
  
  
  
  Review Logs:
  
  Check the system logs (transaction SM21) and the developer trace files (transaction ST11) for any additional error messages or warnings that may provide more context about the issue.
  
  
  
  Restart the Application Server:
  
  After making changes, it may be necessary to restart the SAP application server to ensure that the changes take effect.
  
  
  
  Related Information:
  
  PSE (Personal Security Environment): A PSE is a secure storage area for cryptographic keys and certificates used in secure communications.
  SSF (Secure Store and Forward): SSF is a framework in SAP for handling secure communications, including encryption and digital signatures.
  Transaction Codes:
  
  STRUST: Manage PSEs and certificates.
  SSFC: SSF configuration.
  SM21: System log.
  ST11: Developer traces.
  
  
  
  If the issue persists after following these steps, it may be beneficial to consult SAP support or refer to SAP Notes related to the specific error message for further assistance.