SAP ABAP Message Class SAML2 (SAML2 Messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SEC-LGN-SML (Application Component) SAML 2.0
⤷ SAML2_COMMON (Package) SAML2 Common
⤷ BC-SEC-LGN-SML (Application Component) SAML 2.0
⤷ SAML2_COMMON (Package) SAML2 Common
Attributes
Message class | SAML2 | |
Short Description | SAML2 Messages | |
Changed On | 20140121 | |
Last Changed At | 103753 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | An internal error occurred (message: &1) | The short text describes the object sufficiently | |
2 | 001 | Analysis of XML fragment &1 failed (error message: &2) | The short text describes the object sufficiently | |
3 | 002 | Parameter &1 was either incorrectly set or not set in method &2 | The short text describes the object sufficiently | |
4 | 003 | Error in ST program &1 when importing XML data | Space: object requires documentation | |
5 | 004 | Failed to generate the XML data using ST program &1 | Space: object requires documentation | |
6 | 005 | No entity in with &1 &2 in client &3 found | The short text describes the object sufficiently | |
7 | 006 | Entity &1 in client &2 already exists | The short text describes the object sufficiently | |
8 | 007 | Message '&1' did not arrive at the correct destination | The short text describes the object sufficiently | |
9 | 008 | SSF function &1 returned the error code &2 | Space: object requires documentation | |
10 | 009 | No user found for name ID '&1' (format: &2) | The short text describes the object sufficiently | |
11 | 010 | Identity federation of user &1 (format: &2) failed | The short text describes the object sufficiently | |
12 | 011 | SAML2 in client &1 is not active | The short text describes the object sufficiently | |
13 | 012 | Index&1 does not contain an entity | The short text describes the object sufficiently | |
14 | 013 | Defederation of user &1 (format: &2) failed | The short text describes the object sufficiently | |
15 | 014 | Format '&1' is not supported for user assignment | The short text describes the object sufficiently | |
16 | 015 | Defederation of format '&1' is not supported | The short text describes the object sufficiently | |
17 | 016 | Federation for format '&1' is not supported | The short text describes the object sufficiently | |
18 | 017 | There is no trust between entities &1 and &2 in client &3 | The short text describes the object sufficiently | |
19 | 018 | No user found for name ID '&1' (format: persistent, type: out-of-band) | The short text describes the object sufficiently | |
20 | 019 | Element '&1' is not supported | The short text describes the object sufficiently | |
21 | 020 | The user account of IDP [&1] is not yet federated in system &2 (&3) | Space: object requires documentation | |
22 | 021 | The validation of message '&1' failed | The short text describes the object sufficiently | |
23 | 022 | The assertion issuer is not identical to the response issuer | The short text describes the object sufficiently | |
24 | 023 | Attribute '&1' of element '&2' is invalid | The short text describes the object sufficiently | |
25 | 024 | All 'SubjectConfirmation' elements are invalid | The short text describes the object sufficiently | |
26 | 025 | Attribute '&1' is not identical in all '&2' elements | The short text describes the object sufficiently | |
27 | 026 | '&1' elements reference different users | The short text describes the object sufficiently | |
28 | 027 | Entity &1 is not defined in the element 'AudienceRestriction' | The short text describes the object sufficiently | |
29 | 028 | The assertion has already been consumed | The short text describes the object sufficiently | |
30 | 029 | Element '&1' does not exist | The short text describes the object sufficiently | |
31 | 030 | Authentication context &1 is not supported | The short text describes the object sufficiently | |
32 | 031 | The assertion was not received at end point '&1' | The short text describes the object sufficiently | |
33 | 032 | Could not create session | The short text describes the object sufficiently | |
34 | 033 | Could not terminate session | The short text describes the object sufficiently | |
35 | 034 | Attribute '&1' of element '&2' does not exist | The short text describes the object sufficiently | |
36 | 035 | No user found with alias '&1' (format: unspecified) | The short text describes the object sufficiently | |
37 | 036 | No SAML2 session found | The short text describes the object sufficiently | |
38 | 037 | In client &1 no trusted entity for &2 was found | The short text describes the object sufficiently | |
39 | 038 | Processing of the message failed. SAML status code: [&1] | The short text describes the object sufficiently | |
40 | 039 | Processing of the message failed. Status code [&1] message [&2] | Space: object requires documentation | |
41 | 040 | Holder-of-key certificate not found | The short text describes the object sufficiently | |
42 | 041 | KeyInfo element must not contain any certificate revocation lists (CRLs) | The short text describes the object sufficiently | |
43 | 042 | Calling of URL &1 was terminated during SAML2 processing | The short text describes the object sufficiently | |
44 | 043 | Activate session cookies in the browser and restart the service | The short text describes the object sufficiently | |
45 | 044 | No encrypted data in &1 | The short text describes the object sufficiently | |
46 | 045 | Message &1 is not signed | The short text describes the object sufficiently | |
47 | 046 | The message does not contain an issuer | The short text describes the object sufficiently | |
48 | 047 | SOAP communication failed with code &1 and status &2 | Space: object requires documentation | |
49 | 048 | Access by the SOAP request to &1 was denied with status &2 | Space: object requires documentation | |
50 | 049 | No endpoint with binding &2 is defined for profile &1 | The short text describes the object sufficiently | |
51 | 050 | The authentication of the SOAP request is too weak | The short text describes the object sufficiently | |
52 | 051 | User &1 does not exist in client &2 | The short text describes the object sufficiently | |
53 | 052 | User &1 in client &2 is not of type SERVICE | Space: object requires documentation | |
54 | 053 | Entity &1 in client &3 is not a member of affiliation &2 | The short text describes the object sufficiently | |
55 | 054 | Certificate analysis failed (error value: &1) | Space: object requires documentation | |
56 | 055 | Error &1(&2) occurred during lock/unlock server operation (parameter &3) | The short text describes the object sufficiently | |
57 | 056 | The logon policies do not support the authentication contexts | The short text describes the object sufficiently | |
58 | 057 | Entity &1 is not active in client &2 | Space: object requires documentation | |
59 | 058 | SOAP communication at endpoint &1 requires an HTTP destination | Space: object requires documentation | |
60 | 059 | Entity &1 in client &3 is stillused in logon policy &2 | Space: object requires documentation | |
61 | 060 | Call of function &1 failed with error &2 | The short text describes the object sufficiently | |
62 | 061 | Signature of message '&1' from issuer '&2' is invalid | Space: object requires documentation | |
63 | 062 | Element '&1' is empty | The short text describes the object sufficiently | |
64 | 063 | Decryption of element &1 of message &2 failed | The short text describes the object sufficiently | |
65 | 064 | Logon policy &1 was not found in client &2 | The short text describes the object sufficiently | |
66 | 065 | In client &1 there is already an entity with operation mode &2 | The short text describes the object sufficiently | |
67 | 066 | Trusted entity &1 in client &2 is not of type external | The short text describes the object sufficiently | |
68 | 067 | For entity &1 in client &2 no certificate could be determined | The short text describes the object sufficiently | |
69 | 068 | Authentication failed: No description available | The short text describes the object sufficiently | |
70 | 069 | URL &1 is not defined as a SAML 2.0 enpoint in client &2 | The short text describes the object sufficiently | |
71 | 070 | The configuration forbids the creation of metadata | The short text describes the object sufficiently | |
72 | 071 | Authentication failed: Wrong password | The short text describes the object sufficiently | |
73 | 072 | Authentication failed: User locked by administrator | The short text describes the object sufficiently | |
74 | 073 | Authentication failed: User locked for failed logon attempts | The short text describes the object sufficiently | |
75 | 074 | Authentication failed: CUA - User has not system assignment | The short text describes the object sufficiently | |
76 | 075 | Authentication failed: Wrong user type (for example CPIC/BATCH) | The short text describes the object sufficiently | |
77 | 076 | Authentication failed: No appropriate entry in USREXTID | The short text describes the object sufficiently | |
78 | 077 | Authenication failed: Multiple entries in USREXTID | The short text describes the object sufficiently | |
79 | 078 | Authentication failed: Error during SAML 2.0 logon | The short text describes the object sufficiently | |
80 | 079 | Authentication failed: User account not valid | The short text describes the object sufficiently | |
81 | 080 | Authentication failed: Wrong input parameter | The short text describes the object sufficiently | |
82 | 081 | Authentication failed: User is already logged on | The short text describes the object sufficiently | |
83 | 082 | Authentication failed: No authorization to call | The short text describes the object sufficiently | |
84 | 083 | Profile &1 is not active or known in client &2 | The short text describes the object sufficiently | |
85 | 084 | Validation of the SAML 2 session in client &1 failed | The short text describes the object sufficiently | |
86 | 085 | URI &1 is invalid: Logon in client &2 is not possible | The short text describes the object sufficiently | |
87 | 086 | HTTP data for SAML2 logon in client &1 are too large (>4 KB) | The short text describes the object sufficiently | |
88 | 087 | SAML2 is activated in client &1 | Space: object requires documentation | |
89 | 088 | HTTP security session management is not active in client &1 | Space: object requires documentation | |
90 | 089 | Entity name &1 in client &2 is invalid | Space: object requires documentation | |
91 | 090 | Element '&1' is not encrypted | The short text describes the object sufficiently | |
92 | 091 | No user with email '&1' found | The short text describes the object sufficiently | |
93 | 092 | More than one user with email '&1' found | The short text describes the object sufficiently | |
94 | 093 | No RelayState mapping found for RelayState value &1 | The short text describes the object sufficiently | |
95 | 094 | No default application path is configured for ACS endpoint | The short text describes the object sufficiently | |
96 | 095 | The binding &1 is not supported during &2 processing | The short text describes the object sufficiently | |
97 | 096 | The '&1' is not a correct URI | The short text describes the object sufficiently | |
98 | 097 | The destination '&1' does not exist | The short text describes the object sufficiently | |
99 | 098 | Error in simple transformation program &1: &2 | The short text describes the object sufficiently | |
100 | 099 | System expected one of the digest algorithms: &1, but received &2 | Space: object requires documentation | |
101 | 100 | Signature algorithm '&1' is out of the required hash algorithms: &2 | The short text describes the object sufficiently | |
102 | 101 | Erroneous application path | The short text describes the object sufficiently | |
103 | 102 | Signing certificate of the SOAP message is not trusted | The short text describes the object sufficiently | |
104 | 103 | Importing PSE error: '&1' | The short text describes the object sufficiently | |
105 | 104 | The validity of the HoK assertion is not in the defined period of &1 min | The short text describes the object sufficiently | |
106 | 105 | Certificate cannot be saved in Address Book | The short text describes the object sufficiently | |
107 | 106 | Error while saving URL '&1'. Nothing stored. | The short text describes the object sufficiently | |
108 | 107 | Cannot convert certificate from base64 to binary | The short text describes the object sufficiently | |
109 | 108 | PSE was not found | The short text describes the object sufficiently | |
110 | 109 | SSF application cannot be deleted | The short text describes the object sufficiently | |
111 | 110 | PSE unlock failed | The short text describes the object sufficiently | |
112 | 111 | No entity descriptor is selected to be included in the metadata | The short text describes the object sufficiently | |
113 | 112 | Cannot get metadata for selected entity descriptors | The short text describes the object sufficiently | |
114 | 113 | Certificates cannot be saved in PSE: '&1' | The short text describes the object sufficiently | |
115 | 114 | Can not create new UUID | The short text describes the object sufficiently | |
116 | 115 | Can not convert xml to base 64 string | The short text describes the object sufficiently | |
117 | 116 | Can not calculate entity hash for entity name '&1' | The short text describes the object sufficiently | |
118 | 117 | No local entity was found for mode '&1' | The short text describes the object sufficiently | |
119 | 118 | '&1' entities were found for mode '&2' | The short text describes the object sufficiently | |
120 | 119 | Can not obatin private address book for '&1' SSF application | The short text describes the object sufficiently | |
121 | 120 | Can not get certificate's public key | The short text describes the object sufficiently | |
122 | 121 | Can not create new SXML writer | The short text describes the object sufficiently | |
123 | 122 | Can not initialize new digital signature writer object | The short text describes the object sufficiently | |
124 | 123 | Error calling &1 transformation: &2 | The short text describes the object sufficiently | |
125 | 124 | Can not create new opaque ID | The short text describes the object sufficiently | |
126 | 125 | Can not convert new opaque ID to base 64 string | The short text describes the object sufficiently | |
127 | 126 | Can not cast object of type &1 to type &2 | The short text describes the object sufficiently | |
128 | 127 | Can not sign xml: &1 | The short text describes the object sufficiently | |
129 | 128 | Name ID value is not supplied | The short text describes the object sufficiently | |
130 | 129 | Version mismatch | The short text describes the object sufficiently | |
131 | 130 | SubjectConfirmation element validation failed | The short text describes the object sufficiently | |
132 | 131 | Decryption of element '&1' failed | The short text describes the object sufficiently | |
133 | 132 | SAML 2.0 attribute '&1' was not found | The short text describes the object sufficiently | |
134 | 133 | Element '&1' is invalid. Reason: '&2' | The short text describes the object sufficiently | |
135 | 134 | Can not create new SSF application. Reason: '&1' | The short text describes the object sufficiently | |
136 | 135 | Name ID format '&1' not accepted | The short text describes the object sufficiently | |
137 | 136 | No assertion provided for validation | The short text describes the object sufficiently | |
138 | 137 | Assertion not validated successfully | The short text describes the object sufficiently | |
139 | 138 | Validation of temporary PSE filename '&1' failed | The short text describes the object sufficiently | |
140 | 139 | Can't get instance of BAdI for user maintenance: '&1' | The short text describes the object sufficiently | |
141 | 140 | Method '&1' from BAdI implementation has thrown an exception: '&2' | The short text describes the object sufficiently | |
142 | 141 | Can't store consumed artifact in DB. Subrc: '&1' | The short text describes the object sufficiently | |
143 | 142 | Only persistent name ID format is supported on register endpoint | The short text describes the object sufficiently | |
144 | 143 | Automatic account creation - response is expected on register endpoint | The short text describes the object sufficiently | |
145 | 144 | Unknown trusted entity type: '&1' | The short text describes the object sufficiently | |
146 | 145 | Error occured while trying to save the configuration. Subrc: '&1' | The short text describes the object sufficiently | |
147 | 146 | Can't get temporary PSE name. Return code: '&1' | The short text describes the object sufficiently | |
148 | 147 | Can't upload temporary pse file. Subrc: '&1' | The short text describes the object sufficiently | |
149 | 148 | Can't create pse: '&1' | The short text describes the object sufficiently | |
150 | 149 | Can't get PSE name. Return code: '&1' | The short text describes the object sufficiently | |
151 | 150 | Can't load PSE with name '&1'. Return code: '&2' | The short text describes the object sufficiently | |
152 | 151 | Can't download PSE with name '&1'. Return code: '&2' | The short text describes the object sufficiently | |
153 | 152 | Exception occured while trying to import configuration: '&1' | The short text describes the object sufficiently | |
154 | 153 | No PSEs were found in the configuration file. | The short text describes the object sufficiently | |
155 | 154 | Can't map user name. Assertion attribute with name '&1' was not found | The short text describes the object sufficiently | |
156 | 155 | Unknown user ID source: '&1' | The short text describes the object sufficiently | |
157 | 156 | User with alias '&1' does not exist in client '&2' | The short text describes the object sufficiently | |
158 | 157 | Unknown user mapping mode: '&1' | The short text describes the object sufficiently | |
159 | 158 | Problem with endpoint URL '&1' evaluation with regular expression | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in |