Message Number list used by SAP ABAP Class CX_SAML20_CORE (Exceptions Within SAML2 Core Function)
SAP ABAP Class
CX_SAML20_CORE (Exceptions Within SAML2 Core Function) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
![]() |
![]() |
|||
1 | ![]() |
MC - 601 | Object requested is currently locked by user & | |
2 | ![]() |
SAML2 - 107 | Cannot convert certificate from base64 to binary | |
3 | ![]() |
SAML2 - 108 | PSE was not found | |
4 | ![]() |
SAML2 - 106 | Error while saving URL '&1'. Nothing stored. | |
5 | ![]() |
SAML2 - 105 | Certificate cannot be saved in Address Book | |
6 | ![]() |
SAML2 - 104 | The validity of the HoK assertion is not in the defined period of &1 min | |
7 | ![]() |
SAML2 - 103 | Importing PSE error: '&1' | |
8 | ![]() |
SAML2 - 101 | Erroneous application path | |
9 | ![]() |
SAML2 - 096 | The '&1' is not a correct URI | |
10 | ![]() |
SAML2 - 095 | The binding &1 is not supported during &2 processing | |
11 | ![]() |
SAML2 - 094 | No default application path is configured for ACS endpoint | |
12 | ![]() |
SAML2 - 093 | No RelayState mapping found for RelayState value &1 | |
13 | ![]() |
SAML2 - 090 | Element '&1' is not encrypted | |
14 | ![]() |
SAML2 - 089 | Entity name &1 in client &2 is invalid | |
15 | ![]() |
SAML2 - 088 | HTTP security session management is not active in client &1 | |
16 | ![]() |
SAML2 - 086 | HTTP data for SAML2 logon in client &1 are too large (>4 KB) | |
17 | ![]() |
SAML2 - 085 | URI &1 is invalid: Logon in client &2 is not possible | |
18 | ![]() |
SAML2 - 083 | Profile &1 is not active or known in client &2 | |
19 | ![]() |
SAML2 - 082 | Authentication failed: No authorization to call | |
20 | ![]() |
SAML2 - 081 | Authentication failed: User is already logged on | |
21 | ![]() |
SAML2 - 080 | Authentication failed: Wrong input parameter | |
22 | ![]() |
SAML2 - 079 | Authentication failed: User account not valid | |
23 | ![]() |
SAML2 - 078 | Authentication failed: Error during SAML 2.0 logon | |
24 | ![]() |
SAML2 - 077 | Authenication failed: Multiple entries in USREXTID | |
25 | ![]() |
SAML2 - 076 | Authentication failed: No appropriate entry in USREXTID | |
26 | ![]() |
SAML2 - 137 | Assertion not validated successfully | |
27 | ![]() |
SAML2 - 158 | Problem with endpoint URL '&1' evaluation with regular expression | |
28 | ![]() |
SAML2 - 153 | No PSEs were found in the configuration file. | |
29 | ![]() |
SAML2 - 152 | Exception occured while trying to import configuration: '&1' | |
30 | ![]() |
SAML2 - 151 | Can't download PSE with name '&1'. Return code: '&2' | |
31 | ![]() |
SAML2 - 150 | Can't load PSE with name '&1'. Return code: '&2' | |
32 | ![]() |
SAML2 - 149 | Can't get PSE name. Return code: '&1' | |
33 | ![]() |
SAML2 - 148 | Can't create pse: '&1' | |
34 | ![]() |
SAML2 - 147 | Can't upload temporary pse file. Subrc: '&1' | |
35 | ![]() |
SAML2 - 146 | Can't get temporary PSE name. Return code: '&1' | |
36 | ![]() |
SAML2 - 145 | Error occured while trying to save the configuration. Subrc: '&1' | |
37 | ![]() |
SAML2 - 144 | Unknown trusted entity type: '&1' | |
38 | ![]() |
SAML2 - 138 | Validation of temporary PSE filename '&1' failed | |
39 | ![]() |
SAML2 - 075 | Authentication failed: Wrong user type (for example CPIC/BATCH) | |
40 | ![]() |
SAML2 - 136 | No assertion provided for validation | |
41 | ![]() |
SAML2 - 135 | Name ID format '&1' not accepted | |
42 | ![]() |
SAML2 - 134 | Can not create new SSF application. Reason: '&1' | |
43 | ![]() |
SAML2 - 133 | Element '&1' is invalid. Reason: '&2' | |
44 | ![]() |
SAML2 - 132 | SAML 2.0 attribute '&1' was not found | |
45 | ![]() |
SAML2 - 131 | Decryption of element '&1' failed | |
46 | ![]() |
SAML2 - 130 | SubjectConfirmation element validation failed | |
47 | ![]() |
SAML2 - 129 | Version mismatch | |
48 | ![]() |
SAML2 - 113 | Certificates cannot be saved in PSE: '&1' | |
49 | ![]() |
SAML2 - 110 | PSE unlock failed | |
50 | ![]() |
SAML2 - 109 | SSF application cannot be deleted | |
51 | ![]() |
SAML2 - 017 | There is no trust between entities &1 and &2 in client &3 | |
52 | ![]() |
SAML2 - 046 | The message does not contain an issuer | |
53 | ![]() |
SAML2 - 045 | Message &1 is not signed | |
54 | ![]() |
SAML2 - 044 | No encrypted data in &1 | |
55 | ![]() |
SAML2 - 039 | Processing of the message failed. Status code [&1] message [&2] | |
56 | ![]() |
SAML2 - 038 | Processing of the message failed. SAML status code: [&1] | |
57 | ![]() |
SAML2 - 037 | In client &1 no trusted entity for &2 was found | |
58 | ![]() |
SAML2 - 034 | Attribute '&1' of element '&2' does not exist | |
59 | ![]() |
SAML2 - 029 | Element '&1' does not exist | |
60 | ![]() |
SAML2 - 023 | Attribute '&1' of element '&2' is invalid | |
61 | ![]() |
SAML2 - 021 | The validation of message '&1' failed | |
62 | ![]() |
SAML2 - 019 | Element '&1' is not supported | |
63 | ![]() |
SAML2 - 047 | SOAP communication failed with code &1 and status &2 | |
64 | ![]() |
SAML2 - 012 | Index&1 does not contain an entity | |
65 | ![]() |
SAML2 - 011 | SAML2 in client &1 is not active | |
66 | ![]() |
SAML2 - 008 | SSF function &1 returned the error code &2 | |
67 | ![]() |
SAML2 - 007 | Message '&1' did not arrive at the correct destination | |
68 | ![]() |
SAML2 - 006 | Entity &1 in client &2 already exists | |
69 | ![]() |
SAML2 - 005 | No entity in with &1 &2 in client &3 found | |
70 | ![]() |
SAML2 - 004 | Failed to generate the XML data using ST program &1 | |
71 | ![]() |
SAML2 - 003 | Error in ST program &1 when importing XML data | |
72 | ![]() |
SAML2 - 002 | Parameter &1 was either incorrectly set or not set in method &2 | |
73 | ![]() |
SAML2 - 001 | Analysis of XML fragment &1 failed (error message: &2) | |
74 | ![]() |
SAML2 - 000 | An internal error occurred (message: &1) | |
75 | ![]() |
SAML2 - 062 | Element '&1' is empty | |
76 | ![]() |
SAML2 - 073 | Authentication failed: User locked for failed logon attempts | |
77 | ![]() |
SAML2 - 072 | Authentication failed: User locked by administrator | |
78 | ![]() |
SAML2 - 071 | Authentication failed: Wrong password | |
79 | ![]() |
SAML2 - 070 | The configuration forbids the creation of metadata | |
80 | ![]() |
SAML2 - 069 | URL &1 is not defined as a SAML 2.0 enpoint in client &2 | |
81 | ![]() |
SAML2 - 068 | Authentication failed: No description available | |
82 | ![]() |
SAML2 - 067 | For entity &1 in client &2 no certificate could be determined | |
83 | ![]() |
SAML2 - 066 | Trusted entity &1 in client &2 is not of type external | |
84 | ![]() |
SAML2 - 065 | In client &1 there is already an entity with operation mode &2 | |
85 | ![]() |
SAML2 - 064 | Logon policy &1 was not found in client &2 | |
86 | ![]() |
SAML2 - 063 | Decryption of element &1 of message &2 failed | |
87 | ![]() |
SAML2 - 074 | Authentication failed: CUA - User has not system assignment | |
88 | ![]() |
SAML2 - 061 | Signature of message '&1' from issuer '&2' is invalid | |
89 | ![]() |
SAML2 - 060 | Call of function &1 failed with error &2 | |
90 | ![]() |
SAML2 - 059 | Entity &1 in client &3 is stillused in logon policy &2 | |
91 | ![]() |
SAML2 - 058 | SOAP communication at endpoint &1 requires an HTTP destination | |
92 | ![]() |
SAML2 - 057 | Entity &1 is not active in client &2 | |
93 | ![]() |
SAML2 - 055 | Error &1(&2) occurred during lock/unlock server operation (parameter &3) | |
94 | ![]() |
SAML2 - 054 | Certificate analysis failed (error value: &1) | |
95 | ![]() |
SAML2 - 053 | Entity &1 in client &3 is not a member of affiliation &2 | |
96 | ![]() |
SAML2 - 050 | The authentication of the SOAP request is too weak | |
97 | ![]() |
SAML2 - 049 | No endpoint with binding &2 is defined for profile &1 | |
98 | ![]() |
SAML2 - 048 | Access by the SOAP request to &1 was denied with status &2 |