Hierarchy
⤷ BC-SEC (Application Component) Security
⤷ STRUST (Package) PKI Management
Basic Data
Data Element | CR_PROFILE_STRICT |
Short Description | Profile Strict |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1_X | |
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 | Strict |
Medium | 10 | Strict |
Long | 10 | Strict |
Heading | 10 | Strict |
Documentation
Definition
Determines the reaction of the system, when it is unable to obtain a certificate revocation list (CRL). Reasons the system cannot obtain a CRL are as follows:
- The system attempted to download the CRL from the source, but was unable to do so; for example, a network failure.
When this happens, the system records the failed access attempt in the database.
- The system determines that there was a failed access attempt, as above, and the configured wait time for that issuer has not been exceeded yet.
The wait time is a parameter of the source list. If the wait time has been exceeded, the system attempts to access the URL in the source list again.
- The system must perform a certificate revocation check on a certificate, for which there is no entry for that issuer in the source list and there is no distribution point listed in the certificate itself.
For any of the situations above, the system returns the status UNKNOWN for the certificate revocation check. Whether the system accepts a certificate with the status UNKNOWN is controlled by the Strict parameter.
Use
Deselect the Strict check box for functions, where the certificate revocation check is not essential; where an occaisional network failure should not hinder your process. A strict profile interprets certificates with the status UNKNOWN as invalid.
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in |