How To Fix WSS050 - &1 records deleted from the Security Token Cache (ts: exp:&2, cre:&3)

SAP Error Message - Details

• Message type: E = Error

• Message class: WSS - Web Services Security

• Message number: 050

• Message text: &1 records deleted from the Security Token Cache (ts: exp:&2, cre:&3)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message WSS050 - &1 records deleted from the Security Token Cache (ts: exp:&2, cre:&3) ?

  Certainly! Here's a detailed explanation of the SAP error message:
  
  SAP Error Message: WSS050 &1 records deleted from the Security Token Cache (ts: exp:&2, cre:&3)
  
  1. Cause
  
  This message indicates that a certain number of entries (&1) have been deleted from the Security Token Cache.
  The Security Token Cache stores security tokens used for authentication and authorization in SAP Web Services Security (WS-Security).
  Tokens have a timestamp with:
  
  exp: expiration time (&2)
  cre: creation time (&3)
  
  
  When tokens expire or become invalid (e.g., due to timeout or security policy), they are removed from the cache to maintain security and optimize memory usage.
  This message is informational and typically occurs during normal cache cleanup operations.
  It can also happen if the system detects expired or stale tokens that should no longer be valid.
  
  
  2. Solution
  
  Generally, no action is required if this message appears occasionally, as it is part of normal cache maintenance.
  If you observe frequent or unexpected deletions, consider:
  
  Checking the token lifetime settings in the Web Services Security configuration.
  Reviewing the system time synchronization between client and server to avoid premature token expiration.
  Ensuring that the security token cache size and cleanup intervals are properly configured.
  
  
  If this message is accompanied by authentication failures or other errors, investigate the token issuance and validation process.
  You can monitor and adjust parameters related to WS-Security tokens in transaction STRUST or via relevant Web Services configuration.
  
  
  3. Related Information
  
  Transaction / Tools:
  
  STRUST – Manage certificates and security tokens.
  SMICM – Check ICM logs for related errors.
  SOAMANAGER – Configure Web Services and security policies.
  
  
  SAP Notes:
  
  Look for notes related to WS-Security token cache management or token expiration issues.
  
  
  Parameters:
  
  Token lifetime and cache cleanup intervals can be influenced by profile parameters or Web Services configuration.
  
  
  Logs:
  
  Check system logs (SM21) and Web Services logs for related warnings or errors.
  
  
  Documentation:
  
  SAP Help Portal on WS-Security and token management.
  SAP Web Services Security Guide.
  
  
  
  
  Summary
  
  
  
  Aspect
  Description
  
  
  
  
  Message
  WSS050 &1 records deleted from Security Token Cache (ts: exp:&2, cre:&3)
  
  
  Cause
  Expired or invalid security tokens removed from cache during cleanup
  
  
  Solution
  Usually no action needed; verify token lifetime and system time if frequent
  
  
  Related Info
  STRUST, SOAMANAGER, SAP Notes, system logs
  
  
  
  
  If you need help with a specific scenario or further troubleshooting, please provide additional context such as system version, frequency of the message, or related errors.