SAML2 - SAML2 Nachrichten
The following messages are stored in message class SAML2: SAML2 Nachrichten.
It is part of development package SAML2_COMMON in software component BC-SEC-LGN-SML. This development package consists of objects that can be grouped under "SAML2 Common".
It is part of development package SAML2_COMMON in software component BC-SEC-LGN-SML. This development package consists of objects that can be grouped under "SAML2 Common".
Message Nr ▲ | Message Text |
|---|---|
| 000 | An internal error occurred (message: &1) |
| 001 | Analysis of XML fragment &1 failed (error message: &2) |
| 002 | Parameter &1 was either incorrectly set or not set in method &2 |
| 003 | Error in ST program &1 when importing XML data |
| 004 | Failed to generate the XML data using ST program &1 |
| 005 | No entity in with &1 &2 in client &3 found |
| 006 | Entity &1 in client &2 already exists |
| 007 | Message '&1' did not arrive at the correct destination |
| 008 | SSF function &1 returned the error code &2 |
| 009 | No user found for name ID '&1' (format: &2) |
| 010 | Identity federation of user &1 (format: &2) failed |
| 011 | SAML2 in client &1 is not active |
| 012 | Index&1 does not contain an entity |
| 013 | Defederation of user &1 (format: &2) failed |
| 014 | Format '&1' is not supported for user assignment |
| 015 | Defederation of format '&1' is not supported |
| 016 | Federation for format '&1' is not supported |
| 017 | There is no trust between entities &1 and &2 in client &3 |
| 018 | No user found for name ID '&1' (format: persistent, type: out-of-band) |
| 019 | Element '&1' is not supported |
| 020 | The user account of IDP [&1] is not yet federated in system &2 (&3) |
| 021 | The validation of message '&1' failed |
| 022 | The assertion issuer is not identical to the response issuer |
| 023 | Attribute '&1' of element '&2' is invalid |
| 024 | All 'SubjectConfirmation' elements are invalid |
| 025 | Attribute '&1' is not identical in all '&2' elements |
| 026 | '&1' elements reference different users |
| 027 | Entity &1 is not defined in the element 'AudienceRestriction' |
| 028 | The assertion has already been consumed |
| 029 | Element '&1' does not exist |
| 030 | Authentication context &1 is not supported |
| 031 | The assertion was not received at end point '&1' |
| 032 | Could not create session |
| 033 | Could not terminate session |
| 034 | Attribute '&1' of element '&2' does not exist |
| 035 | No user found with alias '&1' (format: unspecified) |
| 036 | No SAML2 session found |
| 037 | In client &1 no trusted entity for &2 was found |
| 038 | Processing of the message failed. SAML status code: [&1] |
| 039 | Processing of the message failed. Status code [&1] message [&2] |
| 040 | Holder-of-key certificate not found |
| 041 | KeyInfo element must not contain any certificate revocation lists (CRLs) |
| 042 | Calling of URL &1 was terminated during SAML2 processing |
| 043 | Activate session cookies in the browser and restart the service |
| 044 | No encrypted data in &1 |
| 045 | Message &1 is not signed |
| 046 | The message does not contain an issuer |
| 047 | SOAP communication failed with code &1 and status &2 |
| 048 | Access by the SOAP request to &1 was denied with status &2 |
| 049 | No endpoint with binding &2 is defined for profile &1 |
| 050 | The authentication of the SOAP request is too weak |
| 051 | User &1 does not exist in client &2 |
| 052 | User &1 in client &2 is not of type SERVICE |
| 053 | Entity &1 in client &3 is not a member of affiliation &2 |
| 054 | Certificate analysis failed (error value: &1) |
| 055 | Error &1(&2) occurred during lock/unlock server operation (parameter &3) |
| 056 | The logon policies do not support the authentication contexts |
| 057 | Entity &1 is not active in client &2 |
| 058 | SOAP communication at endpoint &1 requires an HTTP destination |
| 059 | Entity &1 in client &3 is stillused in logon policy &2 |
| 060 | Call of function &1 failed with error &2 |
| 061 | Signature of message '&1' from issuer '&2' is invalid |
| 062 | Element '&1' is empty |
| 063 | Decryption of element &1 of message &2 failed |
| 064 | Logon policy &1 was not found in client &2 |
| 065 | In client &1 there is already an entity with operation mode &2 |
| 066 | Trusted entity &1 in client &2 is not of type external |
| 067 | For entity &1 in client &2 no certificate could be determined |
| 068 | Authentication failed: No description available |
| 069 | URL &1 is not defined as a SAML 2.0 enpoint in client &2 |
| 070 | The configuration forbids the creation of metadata |
| 071 | Authentication failed: Wrong password |
| 072 | Authentication failed: User locked by administrator |
| 073 | Authentication failed: User locked for failed logon attempts |
| 074 | Authentication failed: CUA - User has not system assignment |
| 075 | Authentication failed: Wrong user type (for example CPIC/BATCH) |
| 076 | Authentication failed: No appropriate entry in USREXTID |
| 077 | Authenication failed: Multiple entries in USREXTID |
| 078 | Authentication failed: Error during SAML 2.0 logon |
| 079 | Authentication failed: User account not valid |
| 080 | Authentication failed: Wrong input parameter |
| 081 | Authentication failed: User is already logged on |
| 082 | Authentication failed: No authorization to call |
| 083 | Profile &1 is not active or known in client &2 |
| 084 | Validation of the SAML 2 session in client &1 failed |
| 085 | URI &1 is invalid: Logon in client &2 is not possible |
| 086 | HTTP data for SAML2 logon in client &1 are too large (>4 KB) |
| 087 | SAML2 is activated in client &1 |
| 088 | HTTP security session management is not active in client &1 |
| 089 | Entity name &1 in client &2 is invalid |
| 090 | Element '&1' is not encrypted |
| 091 | No user with email '&1' found |
| 092 | More than one user with email '&1' found |
| 093 | No RelayState mapping found for RelayState value &1 |
| 094 | No default application path is configured for ACS endpoint |
| 095 | The binding &1 is not supported during &2 processing |
| 096 | The '&1' is not a correct URI |
| 097 | The destination '&1' does not exist |
| 098 | Error in simple transformation program &1: &2 |
| 099 | System expected one of the digest algorithms: &1, but received &2 |
| 100 | Signature algorithm '&1' is out of the required hash algorithms: &2 |
| 101 | Erroneous application path |
| 102 | Signing certificate of the SOAP message is not trusted |
| 103 | Importing PSE error: '&1' |
| 104 | The validity of the HoK assertion is not in the defined period of &1 min |
| 105 | Certificate cannot be saved in Address Book |
| 106 | Error while saving URL '&1'. Nothing stored. |
| 107 | Cannot convert certificate from base64 to binary |
| 108 | PSE was not found |
| 109 | SSF application cannot be deleted |
| 110 | PSE unlock failed |
| 111 | No entity descriptor is selected to be included in the metadata |
| 112 | Cannot get metadata for selected entity descriptors |
| 113 | Certificates cannot be saved in PSE: '&1' |
| 114 | Can not create new UUID |
| 115 | Can not convert xml to base 64 string |
| 116 | Can not calculate entity hash for entity name '&1' |
| 117 | No local entity was found for mode '&1' |
| 118 | '&1' entities were found for mode '&2' |
| 119 | Can not obatin private address book for '&1' SSF application |
| 120 | Can not get certificate's public key |
| 121 | Can not create new SXML writer |
| 122 | Can not initialize new digital signature writer object |
| 123 | Error calling &1 transformation: &2 |
| 124 | Can not create new opaque ID |
| 125 | Can not convert new opaque ID to base 64 string |
| 126 | Can not cast object of type &1 to type &2 |
| 127 | Can not sign xml: &1 |
| 128 | Name ID value is not supplied |
| 129 | Version mismatch |
| 130 | SubjectConfirmation element validation failed |
| 131 | Decryption of element '&1' failed |
| 132 | SAML 2.0 attribute '&1' was not found |
| 133 | Element '&1' is invalid. Reason: '&2' |
| 134 | Can not create new SSF application. Reason: '&1' |
| 135 | Name ID format '&1' not accepted |
| 136 | No assertion provided for validation |
| 137 | Assertion not validated successfully |
| 138 | Validation of temporary PSE filename '&1' failed |
| 139 | Can't get instance of BAdI for user maintenance: '&1' |
| 140 | Method '&1' from BAdI implementation has thrown an exception: '&2' |
| 141 | Can't store consumed artifact in DB. Subrc: '&1' |
| 142 | Only persistent name ID format is supported on register endpoint |
| 143 | Automatic account creation - response is expected on register endpoint |
| 144 | Unknown trusted entity type: '&1' |
| 145 | Error occured while trying to save the configuration. Subrc: '&1' |
| 146 | Can't get temporary PSE name. Return code: '&1' |
| 147 | Can't upload temporary pse file. Subrc: '&1' |
| 148 | Can't create pse: '&1' |
| 149 | Can't get PSE name. Return code: '&1' |
| 150 | Can't load PSE with name '&1'. Return code: '&2' |
| 151 | Can't download PSE with name '&1'. Return code: '&2' |
| 152 | Exception occured while trying to import configuration: '&1' |
| 153 | No PSEs were found in the configuration file. |
| 154 | Can't map user name. Assertion attribute with name '&1' was not found |
| 155 | Unknown user ID source: '&1' |
| 156 | User with alias '&1' does not exist in client '&2' |
| 157 | Unknown user mapping mode: '&1' |
| 158 | Problem with endpoint URL '&1' evaluation with regular expression |
| 159 | Unexpected exception during SAML 2.0 processing: '&1' |
| 160 | Undefined source of SAMLResponse. Must be either parameter or header. |
| 161 | Please wait |
| 162 | Note: Your browser does not support JavaScript or it is turned off. |
| 163 | Press the button to proceed. |
| 164 | Missing authorization. (Authorization-Object: &1) |
| 165 | Can't encrypt string: '&1' |
| 166 | Can't decrypt string: '&1' |
| 167 | Entity &1 in client &3 is still used by OAuth 2.0 Client &2 |
| 170 | Operation not possible in the moment (Upgrade is running). |
| 180 | No user found with SAP Global User ID '&1' (format: unspecified) |
| 181 | User with SAP Global User ID '&1' does not exist in client '&2' |
| 182 | No SAP Global User ID found for User '&1' |
| 183 | No email found for User '&1' |