Hierarchy

⤷

⤷

Basic Data
Data Element | CERTSTATUS_SOURCE |
Short Description | Source |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CERTSTATUS_SOURCE | |
Data Type | CHAR | Character String |
Length | 7 | |
Decimal Places | 0 | |
Output Length | 7 | |
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 | Source |
Medium | 10 | Source |
Long | 20 | Source of Entry |
Heading | 45 | Source of Entry |
Documentation
Definition
Indicates where the ABAP system gets information for the revocation or blocking status of certificates. Possible sources are as follows:
- Manual
The ABAP system gets the information from local database tables, namely the Certificate Status List and the Blocking List for Certificate Ranges.
A system administrator adds certificates to these tables, by manually blocking them. The responsible certification authority (CA) may still consider the certificate valid, but the certificate revocation check blocks acceptance of the certificate.
- CRL
The ABAP system gets the information from a certificate revocation list (CRL). The source list for the relevant profile indicates the URL from which the ABAP system downloaded the CRL
The CA has revoked the certificate and listed it in a certificate revocation list (CRL).
Use
You can set the Source field when configuring the source list for an issuer of a certificate.
- To check the certificate status only from the local tables, set the Source field to Manual. This means you do not rely on CRLs distributed by the CA responsible for those certificates.
- Otherwise, set the Source field to CRL.
In the database tables, Certificate Status List and Blocking List for Certificate Ranges, the Source field enables you to determine if the certificate was blocked by an administrator or revoked by a CA.
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in |