SAP ABAP Data Element CERT_MAPPING_USER (Mapped user name)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SEC (Application Component) Security
⤷
SUSR_CERT (Package) User Administration: Certificate administration

⤷

⤷

Basic Data
Data Element | CERT_MAPPING_USER |
Short Description | Mapped user name |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | STRG | Character String of Variable Length |
Length | 0 | |
Decimal Places | 0 | |
Output Length | 0 | |
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 | User |
Medium | 20 | User Name |
Long | 30 | User Name |
Heading | 30 | User Name |
Documentation
Definition
The user name value is the result of the certificate mapping
Use
Dependencies
Example
We have a rule with certificate entry "Subject", certificate attribute "CN" and logon with "User Name". The following subjects are mapped by the rule as follows:
- "CN=SAP_USER, C=DE, O=SAP": User SAP_USER
- "CN=INVALID_SAP_USER, C=DE, O=SAP": User INVALID_SAP_USER
It is important to notice that the value of subject attribute CN is directly copied to the user name field. More precisely, there is no consistency check on the mapped value. The user INVALID_SAP_USER as an example is no valid user name as it is too long.
If the rule maps with the alias instead of the user name, the application tries to retrieve the corresponding user name (of the alias). In case it exists the field shows the user name. Otherwise, the field stays empty.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 731 |