Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SEC (Application Component) Security⤷
SOAP_SECURITY_RD (Package) Release-Dependent Parts of SOAP_SECURITY
Basic Data
| Data Element | SEC_WSS_SETUP_REPLAY_CFG |
| Short Description | Detect message replays |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Provider |
| Medium | 20 | Provider |
| Long | 20 | Provider Setup |
| Heading | 50 | Provider Configuration for Secure Conversation |
Documentation
Definition
A Web Service consumer calls a service on a provider system. Such messages may be intercepted and replayed, to re-execute the same operation.
WS-Security offers two counter measures to prevent message replays.
Timestamps
Messages protected by WS Security contain timestamps. When configured for WS-Security, providers reject messages outside the timeframe specified by the timestamps and clock skew.
Signatures
SOAP messages containing an WS Security header with XML Signatures can be used to check for replays. When replay detection is enabled, the system will store all signature values for 60 minutes and reject messages with an identical signature value. As messages differ by elements like timestamps, message id, the same signature value is not expected.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 702 |
