SINAZE0000 | FileBasedAuthzStoreImpl: Storage cannot be loaded: {0} |
Explanation |
Role storage (roles.txt) can not be loaded. |
Action |
Check the existance of the roles.txt file or the relevant storage. |
SINAZE0001 | FileBasedAuthzStoreImpl: Storage location {0} is missing. |
Explanation |
Role storage (roles.txt) is missing. |
Action |
The location passed to the service does not point to the existing file/storage. Check the availablity to the file. |
SINAZE0002 | Cannot open storage file {0} |
Explanation |
Role storage (roles.txt) cannot be opened. |
Action |
Check if the storage (file) is available and accessible. |
SINAZE0003 | {0} is not readable! |
Explanation |
Role storage (roles.txt) cannot be read. |
Action |
Check if the storage (file) has proper access rights, and whether it is not locked. |
SINAZE0004 | Invalid entry in storage file. Invalid line in the storage file. |
Explanation |
Role storage (roles.txt) syntax is not correct. Invalide entry is found. |
Action |
Check the storage (file) and validate the syntax. |
SINAZE0005 | cannot open {0} |
Explanation |
Role storage (roles.txt) cannot be opened/accessed. |
Action |
Check the storage (file). |
SINAZE0006 | Cannot write to storage file {0}. File does not exist. |
Explanation |
Cannot write to storage file. File does not exist. |
Action |
Chech the availability of the storage/file. |
SINAZE0007 | {0} is not writable! |
Explanation |
Role storage (roles.txt) is not editable. |
Action |
Check access rights for the storage file. |
SINESE0000 | /{0} not found. |
Explanation |
Internal error. A file used by the product is missing. |
Action |
Contact SoftwareAG global support. |
SINESE0001 | Error loading /{0} |
Explanation |
Internal error. A file used by the product cannot be processed. |
Action |
Contact SoftwareAG global support. |
SINESE0002 | /{0} not found. |
Explanation |
Internal error. A validation properties file used by the product is missing. |
Action |
Contact SoftwareAG global support. |
SINESE0003 | Error loading /{0} |
Explanation |
Internal error. A validation properties file used by the product cannot be processed. |
Action |
Contact SoftwareAG global support. |
SINESE0004 | Unknown System Type! |
Explanation |
System type cannot be recognized. |
Action |
Contact SoftwareAG global support. |
SINESE0005 | System property {0} is set, but file '{1}' doesn't exist |
Explanation |
System property com.softwareag.sin.esapi.resources has a value that points to an invalid file or a file that doesn't have proper rights. |
Action |
Check the value of the system property com.softwareag.sin.esapi.resources and update it to point to a valid readable ESAPI.properties file. |
SINJCE0003 | Initialize: JAAS property not set: {0} |
Explanation |
The login module requires a 'DUMMY_USER_PROPERTY_URL' option representing a URL to the user properties file to load, but such option is not configured. |
Action |
Configure a 'DUMMY_USER_PROPERTY_URL' option for the DummyLoginModule. The option value must be a URL to a standard Java properties file containing users, groups and roles information. |
SINLDE0048 | Authentication failed |
Explanation |
LDAPLoginModule - authentication against LDAP failed. User name or password are wrong. |
Action |
Re-enter the user name and password. Check if their values are correct. |
SINLDE0056 | No configured servers. |
Explanation |
No configured servers were found. |
Action |
Ensure that the servers are configured properly. |
SINLDE0057 | No configured servers. |
Explanation |
No configured servers were found. |
Action |
Ensure that the servers are configured properly. |
SINLDE0058 | No configured servers. |
Explanation |
No configured servers were found. |
Action |
Ensure that the servers are configured properly. |
SINLDE0059 | No configured servers. |
Explanation |
No configured servers were found. |
Action |
Ensure that the servers are configured properly. |
SINLDE0060 | LDAP keystore load error |
Explanation |
An error occurred during extraction of a keystore. Possible causes are invalid URL, invalid algorithm, invalid certificate, invalid argument, etc. |
Action |
Ensure that the requested keystore and its URL are valid. |
SINLDE0061 | LDAP truststore load error. |
Explanation |
An error occurred during extraction of a truststore. Possible causes are invalid URL, invalid algorithm, invalid certificate, invalid argument, etc. |
Action |
Ensure that the requested truststore and its URL are valid. |
SINLDE0062 | This principal {0} is with wrong type. Should be {1} |
Explanation |
An error occurred while checking principal type. The principal type must be GROUP_TYPE. |
Action |
Change the principal type to GROUP_TYPE. |
SINLDW0063 | More than one result returned uidprop: {0} uid: {1} |
Explanation |
A single result is expected when getting DN from UID. |
Action |
Ensure that the UID contains a single DN corresponding to the search filter. |
SINLDW0064 | More than one result returned gidprop: {0} gid: {1} |
Explanation |
A single result is expected when getting DN from GID. |
Action |
Ensure that the GID contains a single DN corresponding to the search filter. |
SINLDW0066 | Problem listing group properties. |
Explanation |
An issue has occurred while listing group properties. |
Action |
Ensure that the group properties are valid. |
SINLDW0067 | Empty [DN Prefix/Sufix] |
Explanation |
Empty DN Prefix and DN Sufix were found when listing users during an LDAP configuration. |
Action |
Ensure that the DN Prefix and/or DN Sufix are present. |
SINLDW0070 | Problem checking if DN is a group. |
Explanation |
There was an issue while checking if the DN is a group when trying to get the group ID. |
Action |
Ensure that the DN is a group. |
SINLDW0071 | Problem checking if dn is a user |
Explanation |
There was an issue while checking if the DN is a user when trying to get the user ID |
Action |
Ensure that the DN is a user. |
SINLDW0081 | Property {0} is unknown, but is found in server configuraion. Please check spelling of the properties. |
Explanation |
A wrong property was found in the server configuration. Properties are case sensitive. |
Action |
Check the spelling and capitalization of the properties in the server configuration. |
SINLME0012 | Initialize: failed to create X509CRL from the CRL URL: {0} {1} |
Explanation |
CRLException was thrown during the initialization of the CRL. Possible reasons: the CRL file is broken or it is not in CRL format - http://docs.oracle.com/javase/7/docs/api/java/security/cert/X509CRL.html. |
Action |
Double check in the JAAS configuration the value of the "crl_url" property and verify if the defined CRL file is a valid CRL file. |
SINLME0013 | Initialize: failed to create URL or InputStream from the CRL URL: {0} {1} |
Explanation |
IOException exception diring initialization of the CRL. Possible reasons: the URL is broken or the file is not found. |
Action |
Double check in the JAAS configuration the value of the "crl_url" property and verify if this is a valid URL. If the CRL is on the file system, make sure the value for the "crl_url" begins with "file://". |
SINLME0014 | Initialize: failed to create CRL - CRL location: {0} {1} |
Explanation |
Unknown exception diring initialization of the CRL. |
Action |
Double check the log files about the exception type and the explanation. |
SINLME0015 | Initialize: CRL location is not specified. |
Explanation |
The "check_crl_status" property is set to true but the "crl_url" property is not set up. |
Action |
1. Disable CRL check by setting up the "check_crl_status" property to false or by removing it; 2. Specify the "crl_url" property correctly. |
SINLME0190 | login: unsupported callback {0} |
Explanation |
Supplied CallBack is not supported. Software AG Security Infrastructure supports only SagCredentialCallback, PasswordCallback and NameCallback. |
Action |
Check which Callback is used. |
SINLME0191 | Engine failed to load with options: {0} |
Explanation |
Authentication failed in RoleLoginModule. Storage is not loaded properly. |
Action |
Check logs for more details about the reasons. |
SINLME0192 | Provider class cannot be found {0} |
Explanation |
Role storage implementation provider is not found. |
Action |
Check the value of the "provider_class" property in the JAAS configuration file. |
SINLME0193 | Provider class cannot be instantiated {0} |
Explanation |
Role storage implementation provider cannot be instantiated. |
Action |
Check the value of the "provider_class" property in the JAAS configuration file. |
SINLME0194 | Provider class cannot be accessible {0} |
Explanation |
Role storage implementation provider class is not accessible. |
Action |
Check the value of the "provider_class" property in JAAS configuration file. Check classloaders, if the requested provider class is available. |
SINLME0195 | resolveArtifact: ArtifactParseException {0} |
Explanation |
An error occurred while parsing the artifact. |
Action |
Check the JAAS configuration. |
SINLME0197 | resolveArtifact: ArtifactParserException {0} |
Explanation |
An error occurred while parsing the artifact. |
Action |
Check the JAAS configuration. |
SINLME0198 | resolveArtifact: Exception {0} |
Explanation |
An error occurred while parsing the artifact. |
Action |
Check the JAAS configuration. |
SINLME0199 | resolveArtifact: no name could be found in the SAML response. Returning NULL. |
Explanation |
No name was found in the parsed artifact and the resolving failed. |
Action |
Check the JAAS configuration and the artifact creator. |
SINLME0204 | authenticate() failed. Principal not available in the servlet request. |
Explanation |
The configuration requires a principal, but the HTTP request does not contain one. |
Action |
Check the JAAS configuration. |
SINLME0205 | authenticate() failed. X509Certificate Chain is not available in the servlet request. |
Explanation |
The configuration requires a certificate, but the HTTP request does not contain one. |
Action |
Check the JAAS configuration. |
SINLME0206 | authenticate() failed. SAML Artifact is not available in the servlet request. |
Explanation |
The configuration requires a SAML artifact, but the HTTP request does not contain one. |
Action |
Check the JAAS configuration. |
SINLME0207 | authenticate() failed. SAML Artifact header field name is not set in the JAAS configuration. |
Explanation |
The configuration expects to find the HTTP header field used to search for a SAML Artifact, but the HTTP header is not set. |
Action |
Check the JAAS configuration. |
SINLME0208 | authenticate() failed. Netegrity SiteMinder is not available in the servlet request. |
Explanation |
The configuration requires a Netegrity SiteMinder, but the HTTP request does not contain one. |
Action |
Check the JAAS configuration. |
SINLME0209 | authenticate() failed. Netegrity SiteMinder header field name is not set in the JAAS configuration. |
Explanation |
The configuration expects to find the HTTP header field used to search for a Netegrity SiteMinder, but the HTTP header is not set. |
Action |
Check the JAAS configuration. |
SINLME0210 | authenticate() failed.'{0}' custom header is not available in the servlet request. |
Explanation |
The configuration requires a custom header name, but the HTTP request does not contain one. |
Action |
Check the JAAS configuration. |
SINLME0211 | authenticate() failed. Custom header name property is not set in the JAAS configuration. |
Explanation |
The configuration expects to find the HTTP header field used to search for a custom header, but the HTTP header is not set. |
Action |
Check the JAAS configuration. |
SINLME0212 | authenticate: SAML Assertion identity provider key not available. Authentication failed. |
Explanation |
The SAML Assertion identity provider key is not available. |
Action |
Check the JAAS configuration. |
SINLME0213 | authenticate: SAML Assertion validation process failed. Authentication failed. |
Explanation |
The SAML Assertion validation process failed. |
Action |
Check the JAAS configuration. |
SINLME0214 | authenticate: no username returned. Authentication failed. |
Explanation |
The SAML assertion does not contain a username. |
Action |
Check the JAAS configuration. |
SINLME0215 | initConfiguration: failed! |
Explanation |
An error was found in the LoginModule configuration. |
Action |
Check the JAAS configuration. |
SINLME0216 | Initialize: trust store location is not specified. The default one will be used: {0}; trust store type: {1} |
Explanation |
The trust store location is not specified and the default one will be used. |
Action |
Check the JAAS configuration. |
SINLME0217 | Initialize: failed to create KeyStore from the trust store URL: {0}, keystore type: {1} |
Explanation |
Failed to create a KeyStore from the trust store url. |
Action |
Check the JAAS configuration. |
SINLME0218 | Failed to read certificate from trust store! |
Explanation |
Failed to read the certificate from the trust store. |
Action |
Check the JAAS configuration. |
SINLME0219 | validateAssertion: no name could be found in the SAML assertion |
Explanation |
The SAML assertion does not contain a username. |
Action |
Check the JAAS configuration. |
SINLME0220 | authenticate() failed. Basic authentication information is not available in the servlet request. |
Explanation |
The configuration requires Basic authentication information, but the HTTP request does not contain it. |
Action |
Check the JAAS configuration. |
SINLME0221 | authenticate() failed. The Authorization header required for Basic authentication is not available in the servlet request. |
Explanation |
The configuration expects to find the Authorization HTTP header, but the HTTP header is not set. |
Action |
Check the JAAS configuration. |
SINLME0222 | initConfiguration: failed! Can not load the key store {0} |
Explanation |
Failed to initiate the configuration on the AppleDSLoginModule. Cannot load truststore. |
Action |
Verify that the location of the truststore is valid, the file is not corrupted and password is not missing or invalid. |
SINLME0223 | Error in parsing the HTTP header cookie: {0} |
Explanation |
An error occurred while authenticating with the AppleDSLoginModule. |
Action |
Make sure that the HTTP request is valid and contains all required headers. |
SINLME0224 | authenticate: There is no cookie header in the HttpServletRequest. |
Explanation |
While trying to authenticate with AppleDSLoginModule, the cookie header could not be found in the HttpServletRequest. |
Action |
Make sure that the HTTP request is valid and contains all required headers. |
SINLME0225 | Cookie is not found in cookie header. |
Explanation |
While trying to authenticate with AppleDSLoginModule, the cookie could not be found in the cookie header. |
Action |
Make sure that the HTTP request is valid and contains all required headers. |
SINLME0226 | Cannot read response data |
Explanation |
A read error occured while trying to parse the input content. |
Action |
Make sure that the HTTP response does not contain corrupted data. |
SINLME0227 | The personal id - {0}, is not returned by the server |
Explanation |
The user principal does not contain a name attribute. The name attribute is expected from the HTTP response. |
Action |
Make sure that HTTP request is present and contains all necessary data. Check whether the login module is configured with the proper personal ID. |
SINLME0228 | AppleUrlCreator could not be created. Invalid parameters. |
Explanation |
An error has occurred while trying to create an instance of AppleUrlCreator. The input parameters are NULL. |
Action |
Make sure that HTTP request is present and contains all necessary data. Check whether the login module is configured with the proper cookie header. |
SINLME0229 | constructURL: Neither URL ({0}), nor URL without query ({1}) is specified |
Explanation |
An error occurred when trying to construct a URL, because the URL is not specified in the configuration. |
Action |
Make sure you correctly specify an URL in the configuration. |
SINLME0230 | constructURL: Application admin password ({0}) is required! |
Explanation |
An error occurred when trying to construct a URL, because the application administrator password is not specified in the configuration. |
Action |
Make sure you correctly specify the application administrator password in the configuration. |
SINLME0231 | Application ID ({0}) is not specified as config property. |
Explanation |
If the auth URL contains an <appId> placeholder, the application ID be must also be specified as a property. |
Action |
Set the application ID property. |
SINLME0232 | Application ID ({0}) is not specified in the URL |
Explanation |
The application ID must be contained in the authentication URL. |
Action |
Make sure that the application ID is contained in the URL. |
SINLME0233 | The IP placeholder - {0}, could not be found in the URL |
Explanation |
The auth URL must contain the IP placeholder. |
Action |
Make sure that the machine IP is contained in the URL. |
SINLME0234 | The application admin password placeholder - {0}, could not be found in the URL |
Explanation |
The auth URL must contain the application admin password placeholder. |
Action |
Make sure that the application admin password placeholder is contained in the URL. |
SINLME0235 | The cookie placeholder - {0}, could not be found in the URL |
Explanation |
The auth URL must contain the cookie placeholder. |
Action |
Make sure that the cookie placeholder is present in the URL. |
SINLME0236 | Cannot create URL from {0} |
Explanation |
An error occurred while trying to create a URL from the auth URL. |
Action |
Make sure that the authentication URL is valid and does not contain any restricted characters. |
SINLME0237 | CookieValidator: Validation failed while reading URL data. |
Explanation |
The URL validation failed while reading URL data. |
Action |
Make sure that the response from the URL does not contains corrupted data. |
SINLME0238 | Validation failed! The URL is not specified. |
Explanation |
The URL validation failed - the URL is NULL. |
Action |
Make sure that the provided authentication URL is valid. |
SINLME0241 | Validation failed! Invalid line in the HTTP response. |
Explanation |
Content validation failed due to an invalid line in the HTTP response. |
Action |
Make sure that the HTTP response does not contain invalid data. |
SINLME0242 | Validation failed! Status code is {0} |
Explanation |
Content validation has failed. |
Action |
Make sure that the HTTP response is successful and has SUCCESS status code. |
SINLME0243 | Required func and returned values are different |
Explanation |
The check of the required principal fails due to inconsistency between the required func and the returned values. |
Action |
Make sure that the property attributes of the principal are not null. |
SINLME0244 | login: username not found: {0} |
Explanation |
The configured properties file that represents the user store of the login module does not contain an entry for the specified user. |
Action |
The properties file that represents the user store of the login module must contain a 'userids' property with a comma-separated list of user identifiers. For each identifier, a separate <identifier>.name property must be configured which represents the human-readable user name. If the username is not found, this means that respective configuration (user identifier and/or name) is not present in the properties file. If the user should be allowed to log in, then this user information must be added to the properties file. |
SINLME0245 | login: passwords don't match for user {0} |
Explanation |
The specified password does not match the configured password for the user. |
Action |
Double-check the specified password. The password for the user is configured via the "<userid>.passhash" property in the properties file configured for the login module. The value of the property is the SHA-1 digest of the plain text password encoded as a hexadecimal number. |
SINLME0246 | login: SHA-1 hashing algorithm not found |
Explanation |
The Java virtual machine does not contain a security provider which supports the SHA-1 hashing algorithm. |
Action |
Make sure you use a Java version which supports SHA-1 hashing algorithm or configure a Java security provider which supports this algorithm. |
SINLME0247 | Resource not found: {0} |
Explanation |
The specified resource file cannot be found in the classpath. |
Action |
Please check if the security infrastructure java archives are not corrupted and whether they contain the mentioned resource. |
SINRME0139 | Wrong password format. |
Explanation |
Password entry for the user is not correct. It must start with "$6a$" or "$6$". |
Action |
Check users.txt file. |
SINRME0140 | Duplicates in user name. |
Explanation |
User names are duplicated in the users.txt. |
Action |
Check the users.txt file that is used. |
SINRME0141 | Duplicates in user name. |
Explanation |
User names are duplicated in the users.txt. |
Action |
Check the users.txt file that is used. |
SINRME0142 | Failed to initialize CipherUtil. |
Explanation |
CipherUtil cannot be initialized due to some of following reasons: missing or invalid algorithm or key; invalid padding scheme; provider doesn't support a CipherSpi implementation for the specified algorithm; provider doesn't support a MacSpi implementation for the specified algorithm; provider doesn't support a SecretKeyFactorySpi implementation for the specified algorithm; the given key specification is inappropriate for this secret-key factory to produce a secret key; the given key is inappropriate for initializing MAC. |
Action |
General security error. Contact SoftwareAG global support. |
SINSCE0000 | URL is missing in configuration! |
Explanation |
Store cannot be added due to missing URL in the configuration. |
Action |
Ensure that a valid URL is specified. |
SINSOE0000 | Cannot initialize Web SSO config context. |
Explanation |
The Web SSO configuration could not be properly initialized. |
Action |
Make sure that your configuration is valid. |
SINSOE0001 | Cannot initialize Web SSO config context. |
Explanation |
The Web SSO configuration could not be properly initialized. |
Action |
Make sure that your configuration is valid. |
SINSOE0002 | Failed to initialize Saml2 engine - all SAML operations will fail. |
Explanation |
Internal error. The Saml2 engine failed to initialize properly. All SAML operations will fail. |
Action |
Contact SoftwareAG global support. |
SINSOE0003 | Error initializing keystore. |
Explanation |
Keystore cannot be found or the credentials are wrong. |
Action |
Ensure that the keystore exists and you have provided valid credentials. |
SINSOE0004 | Error initializing keystore. |
Explanation |
Keystore cannot be found or the credentials are wrong. |
Action |
Ensure that the keystore exists and you have provided valid credentials. |
SINSOE0005 | Cannot load IDPSSODescriptor from metadata. |
Explanation |
The error occured because of invalid IDP metadata. |
Action |
Make sure that the provided IDP metadata is correct and has the SSO services defined. |
SINSOE0006 | Cannot load SPSSODescriptor from metadata. |
Explanation |
The error occured because of invalid SP metadata. |
Action |
Make sure that the provided SP metadata is correct and has the consumer services defined. |
SINSOE0007 | IDP cannot be determined. |
Explanation |
IDP is missing in the metadata. |
Action |
Ensure that you have provided IDP metadata. |
SINSOE0008 | Cannot get dynamic configuration. |
Explanation |
Internal error. The service that provides configurations cannot be obtained. |
Action |
Contact SoftwareAG global support. |
SINSOE0009 | The configuration could not be found. |
Explanation |
Internal error. The service that provides configurations cannot be obtained. |
Action |
Contact SoftwareAG global support. |
SINSOE0010 | The configuration could not be found. |
Explanation |
Internal error. The service that provides configurations cannot be obtained. |
Action |
Contact SoftwareAG global support. |
SINSOE0011 | Configuration Admin service is not available. |
Explanation |
Internal error. The service that provides configurations cannot be obtained. |
Action |
Contact SoftwareAG global support. |
SINSOE0012 | Can't obtain key from the keystore or generate key info for credential: {0}, {1} |
Explanation |
A key cannot be obtained from the keystore with the provided crednetials. |
Action |
Make sure the provided credentials are valid. |
SINSOW0013 | Password for key alias: '{0}' is missing. This might lead to failure to load the respective key from key store |
Explanation |
A password is not provided for the given alias. |
Action |
Check your configuration and add a password for the specified alias. |
SINSOW0014 | Cannot obtain SPSSODescriptor. Default Web SSO profile will be used. |
Explanation |
Cannot fetch metadata for the given provider (SPSSODescriptor). |
Action |
Check whether the Service Provider metadata contains the required data if the usage of the default value is not desired. |
SINSSE0022 | SSOS properties could not be updated after sso properties file creation. Restart may be needed. |
Explanation |
SSO Service properties could not be updated after sso properties file creation. |
Action |
Restart of the SSO service may be needed. |
SINSSE0023 | CacheManager cannot be instantiated. {0} |
Explanation |
CacheManager cannot be instantiated. The service will work without cache. This could cause some performance degradation. |
Action |
Check the value of the "com.softwareag.security.idp.ehcache.location" property in the com.softwareag.sso.pid.properties dynamic configuration file. |
SINSSE0024 | Ehcache cannot be initialized. cacheManager = {0} |
Explanation |
Ehcache cannot be initialized. The cachemanager in not available. |
Action |
Switch logging to debug and check the log file for more details. |
SINSSE0025 | Ehcache in null |
Explanation |
Ehcache in null. |
Action |
Switch logging to debug and check the log file for more details. |
SINSSE0026 | Return NULL. Missing user ID in the assertion. |
Explanation |
Wrong SAML assertion format. The required ID attribute is missing. |
Action |
Check the SAML assertion syntax. |
SINSSE0027 | parseAssertion(String) throws SAMLException {0} |
Explanation |
Parsing of the SAML assertion failed. |
Action |
Activate debug logging and check log file for more details. |
SINSSE0028 | Return NULL. Missing user ID in the assertion. |
Explanation |
Wrong SAML assertion format. The required ID attribute is missing. |
Action |
Check the SAML assertion syntax. |
SINSSE0029 | {0} |
Explanation |
Parsing of the SAML assertion failed. |
Action |
Activate debug logging and check log file for more details. |
SINSSE0030 | generateAssertion() throws GeneralSecurityException {0} |
Explanation |
Generation of the SAML assertion failed with GeneralSecurityException. |
Action |
Activate debug logging and check log file for more details. |
SINSSE0031 | generateAssertion() throws XMLSignatureException {0} |
Explanation |
Generation of the SAML assertion failed with XMLSignatureException. |
Action |
Activate debug logging and check log file for more details. |
SINSSE0032 | generateAssertion() throws MarshalException {0} |
Explanation |
Generation of the SAML assertion failed with MarshalException. |
Action |
Activate debug logging and check log file for more details. |
SINSSE0033 | generateAssertion() throws MarshallingException {0} |
Explanation |
Generation of the SAML assertion failed with MarshallingException. |
Action |
Activate debug logging and check log file for more details. |
SINSSE0034 | Error loading truststore or keystore. Services will be unregistered. |
Explanation |
Keystore or truststore cannot be found or the credentials are missing. |
Action |
Ensure that the keystore/truststore exists and you have provided valid credentials. |
SINSSE0035 | Error loading truststore. Services will be unregistered. |
Explanation |
Truststore cannot be found or the credentials are missing. |
Action |
Ensure that the truststore exists and you have provided valid credentials. |
SINSSE0036 | Error during STS API initialization: {0} |
Explanation |
An algorithm is not supported by the JVM. |
Action |
Ensure that unlimited strength JCE (Java Cryptographic Extension) is available on the system.f If it is available, contact Software AG Global Support. |
SINSSE0037 | Error during AuthResponse generation: {0} |
Explanation |
A signature cannot be created or the element being signed cannot be marshalled. |
Action |
Ensure that the identity provider keystore is available and contains a signing key with the configured alias and credentials. |
SINSSE0038 | Unsupported request type - expected AuthnRequest but was {0} |
Explanation |
The received request is not a SAML AuthnRequest. |
Action |
Ensure the received SAML message is a valid SAML AuthnRequest. |
SINSSE0039 | Error during request parsing: {0} |
Explanation |
The received SAML AuthRequest cannot be parsed. |
Action |
Ensure the received XML message is a valid SAML AuthnRequest message. |
SINSSE0040 | Missing signature in the request, ID: {0} |
Explanation |
The received SAML AuthnRequest does not contain a signature. |
Action |
Ensure the received SAML AuthnRequest is signed by the respective relying party issuing the request. |
SINSSE0041 | Insufficient input data: destination not provided! |
Explanation |
A SAML response cannot be generated due to missing destination URL. |
Action |
Ensure a valid destination URL is provided when generating the SAML Response message. |
SINSSE0042 | Insufficient input data: userId not provided! |
Explanation |
A SAML response cannot be generated due to missing user ID. |
Action |
Ensure valid user ID is provided when generating SAML Response. The user ID is required to generate the SAML assertion's subject information. |
SINSSE0044 | Missing request ID |
Explanation |
Validation of SAML AuthRequest message is failing due to missing ID attribute. |
Action |
Ensure the SAML AuthnRequest message contains a valid ID attribute. |
SINSSE0045 | Missing request issue instant |
Explanation |
Validation of SAML AuthRequest fails due to missing IssueInstant attribute. |
Action |
Ensure the SAML AuthnRequest message contains a valid IssueInstant attribute, which represents the time instant of issue for the request. |
SINSSE0046 | SAML AuthnRequest version is not SAML 2.0 |
Explanation |
The SAML AuthnRequest has invalid Version attribute, the only supported version is SAML 2.0 |
Action |
Ensure SAML AuthnRequest message uses SAML 2.0 version. |
SINSSE0047 | Missing issuer in the request. |
Explanation |
SAML AuthRequest message does not specify an issuer. |
Action |
Ensure the SAML AuthnRequest message specifies an issuer, which identifies the entity that generated the request message. |
SINSSE0048 | No relying party configuration found for entityId {0} |
Explanation |
The identity provider is not configured with a relying party for the given entity identifier. |
Action |
Check if the relying party identified by the specified entityId is trusted, and if so, configure a relying party with this identifier in the identity provider configuration. |
SINSSE0049 | Unexpected signature algorithm: {0} |
Explanation |
The signature algorithm of the received SAML AuthnRequest message does not match the signature algorithm configured for the respective relying party in the identity provider configuration. |
Action |
The expected relying party signature algorithm must be specified in the relying party configuration. To disable checking the signature algorithm, do not configure a signature algorithm for the relying party. |
SINSXE0000 | Initialize: keystore password is not specified. |
Explanation |
Keystore password is missing. |
Action |
Make sure that the keystore password is specified. |
SINSXE0001 | No token returned from IAF. |
Explanation |
Internal error. |
Action |
Contact SoftwareAG global support. |
SINSXE0002 | Signature creation failed. |
Explanation |
Certificate cannot be found or error occurred during signing operation. |
Action |
Make sure that the provided certificate is valid. |
SINSXE0003 | Unsupported encoding. |
Explanation |
Internal error. Encoding with not supported charset. |
Action |
Contact SoftwareAG global support. |
SINSXE0004 | verifySignature: Given certificate is NULL |
Explanation |
Cannot verify given signature. The certificate is missing. |
Action |
Set certificate for verification of the signature. |
SINSXE0005 | Utility path is not specified |
Explanation |
The utility path is not specified in the JAAS configuration. |
Action |
Make sure that the utility path is specified in the JAAS configuration. |
SINSXE0006 | RMI Port must be a valid integer. |
Explanation |
The specified RMI port is invalid. |
Action |
Set a valid RMI port in the configuration. |
SINSXE0007 | Remote classes are not currently bound |
Explanation |
Internal error. |
Action |
Contact Software AG global support. |
SINSXE0008 | Problem with clearing credentials |
Explanation |
Internal error. User credentials cannot be cleared. Logout operation failed. |
Action |
Contact Software AG global support. |
SINSXE0009 | Problem creating repository manager |
Explanation |
Internal error. RMI registry function was not found or could not obtain remote reference to the repository. |
Action |
Contact Software AG global support. |
SINSXE0010 | TEMPLATE_SECTION must not be null or empty. |
Explanation |
Template section option is not specified in the JAAS configuration. |
Action |
Make sure that the template section option is specified in the JAAS condiguration. |
SINSXE0011 | Error opening SSX Repository |
Explanation |
The error is thrown by the SSX repository during opening operation. |
Action |
Make sure that the provided SSX parameters are valid. |
SINSXE0012 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining the remote registry. |
Action |
Contact Software AG global support. |
SINSXE0013 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining the remote registry. |
Action |
Contact Software AG global support. |
SINSXE0014 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining groups from the repository. |
Action |
Contact Software AG global support. |
SINSXE0015 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining users from the repository. |
Action |
Contact Software AG global support. |
SINSXE0016 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining user groups from the repository. |
Action |
Contact Software AG global support. |
SINSXE0017 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining the users in a group from the repository. |
Action |
Contact Software AG global support. |
SINSXE0018 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining the principles in a group from the repository. |
Action |
Contact Software AG global support. |
SINSXE0019 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when checking if a group exists in the repository. |
Action |
Contact Software AG global support. |
SINSXE0020 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when checking if a user exists in the repository. |
Action |
Contact Software AG global support. |
SINSXE0021 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining user principals from the repository. |
Action |
Contact Software AG global support. |
SINSXE0022 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining group principals from the repository. |
Action |
Contact Software AG global support. |
SINSXE0023 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when obtaining the repository type. |
Action |
Contact Software AG global support. |
SINSXE0024 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when specifying page size. |
Action |
Contact Software AG global support. |
SINSXE0025 | Cannot obtain lock |
Explanation |
Internal error. An interruption ocurred when specifying principals data to IAF. |
Action |
Contact Software AG global support. |
SINSXE0026 | LoadAccessList: Cannot read file {0} {1} |
Explanation |
The URL of the load access list is not provided. |
Action |
Make sure that the "load access list" command line option is present. |
SINSXE0027 | This client has no permissions for authentication. Please contact with your RMI server administrator. |
Explanation |
The client has no permissions for authentication. |
Action |
Contact your RMI server administrator. |
SINSXE0028 | authenticate: could not logout. |
Explanation |
Internal error. Logout operation failed. |
Action |
Contact Software AG global support. |
SINSXE0029 | authenticate: could not login the user with credentials: {0} {1} |
Explanation |
Logon failed. |
Action |
Make sure the used credentials are valid. |
SINSXE0030 | logout: user data parameter is null during the remote logout! |
Explanation |
Internal error. Logout operaiton failed. User doesn't exist. |
Action |
Try again later, if that doesn't solve the issue, contact Software AG global support. |
SINSXE0031 | logoutUser: could not logout the user: {0} {1} |
Explanation |
Internal error. Logout operation failed. |
Action |
Contact Software AG global support. |
SINSXE0032 | logoutUser: this context could not be fund in the cache. User data: {0} |
Explanation |
Internal error. Context is missing from the cache. |
Action |
Contact Software AG global support. |
SINSXE0033 | Could not obtain lock |
Explanation |
Internal error. An interruption occured when obtaining the remote registry. |
Action |
Contact Software AG global support. |
SINSXE0034 | Could not obtain lock |
Explanation |
Internal error. An interruption occured when obtaining an acess token frim the remote token manager. |
Action |
Contact Software AG global support. |
SINSXE0035 | Invalid parameter! |
Explanation |
Passed arguments during initialization of the remote SSX server are not registry port or configuration file. |
Action |
Make sure that either URL configuration or port number is present in the command line options. |
SINSXE0036 | key store password parameter is missing |
Explanation |
Keystore password is missing. |
Action |
Provide valid keystore password. |
SINSXE0037 | Error starting the server |
Explanation |
Error occurred during initialization/start of the server. |
Action |
Contact Software AG global support. |
SINSXE0038 | Error running the server |
Explanation |
Internal error. |
Action |
Contact global Software AG support. |
SINSXE0039 | Error unbinding services |
Explanation |
Error occurred during shutdown of the server. |
Action |
Contact Software AG global support. |
SINSXE0040 | Can't get all groups: {0} |
Explanation |
Groups cannot be obtained. The SSX repository cannot be opened. |
Action |
Make sure that the provided SSX repository parameters are valid. If the parameters are correct, contact global Software AG support. |
SINSXE0041 | This principal {0} is with wrong. |
Explanation |
Internal error. The principal has wrong user type. |
Action |
Contact global Software AG support. |
SINSXE0042 | This {0} has wrong type |
Explanation |
This {0} has wrong user type. |
Action |
Contact global Software AG support. |
SINSXE0043 | This {0} is not user. |
Explanation |
Error when verifying user. |
Action |
Contact global Software AG support. |
SINSXE0044 | This principal: {0} has wrong type |
Explanation |
Wrong principal type. |
Action |
Contact global Software AG support. |
SINSXE0045 | This {0} is not group. |
Explanation |
Error when verifying group. |
Action |
Contact global Software AG support. |
SINSXE0046 | This method is not supported! |
Explanation |
Specifying page size is not yet supported. |
Action |
Do not use this method. |
SINSXE0047 | Input data cannot be null |
Explanation |
Input data (password) is missing or incorrect. |
Action |
Make sure that the input data (password) is correct. |
SINSXE0048 | Token type is not IAF token or artifact. |
Explanation |
Access token is invalid, it does not contain a IAF token or artifact. |
Action |
Contact global Software AG support. |
SINSXE0049 | Cannot retrieve access token {0} |
Explanation |
Internal error. Repository cannot be opened. |
Action |
Contact global Software AG support. |
SINSXE0050 | Can not get manifest file. |
Explanation |
Cannot obtain the manifest of the SSX jar file. |
Action |
Contact Software AG global support. |
SINSXE0051 | Can not receive user groups properties. |
Explanation |
Internal error. Native code exceuted. Cannot receive user groups properties. |
Action |
Contact global Software AG support. |
SINSXE0052 | Can not receive user properties. |
Explanation |
Internal error. Native code exceuted. Cannot receive user properties. |
Action |
Contact global Software AG support. |
SINSXE0053 | Can not receive group properties. |
Explanation |
Internal error. Native code exceuted. Cannot receive group properties. |
Action |
Contact global Software AG support. |
SINSXE0054 | Server not responding for a long time. |
Explanation |
Connectivity issues. |
Action |
Contact global Software AG support. |
SINSXE0055 | There is no SAG User Database Module in the manifest file. |
Explanation |
The manifest file of the Software AG security extension java archive does not contain a 'SAG User Database Module' attribute section. |
Action |
Contact Software AG Global Support. |