Security token service module messagesEdit online These messages are provided by the security token service module component. FBTSTM006E The given TokenType or AppliesTo (TokenType/AppliesTo) in the request is not supported by this server's configuration for RequestType RequestType. FBTSTM007E STSModule module_name not found. FBTSTM008E The QName namespace prefix (QName) does not match any defined namespaces. FBTSTM009EThe server did not start correctly.FBTSTM010EA TokenType or AppliesTo must be specified in the request.FBTSTM011EThe date and time are not in the expected UTC format.FBTSTM013EA RequestType must be specified in the request.FBTSTM014E The given RequestType (RequestType) is not supported by this server's configuration. FBTSTM015E Either no configured XPath selected a node from the request, or the given TokenType or AppliesTo (TokenType/AppliesTo) in the request is not supported by this server's configuration for RequestType RequestType and Issuer (Issuer). FBTSTM016E The given Issuer (Issuer) is not supported by this server's configuration. FBTSTM017EThe server could not find the expected token included in the request.FBTSTM018E An incorrect namespace was encountered and received QName, but expected QName. FBTSTM019E The expected namespace URI for the WS-Trust schema was not found in the request.FBTSTM020E An error was encountered when attempting to open file filename. FBTSTM021E Either the properties file (filename) was not found in the classpath or the key (key) returned no data. FBTSTM022EThe message passed to the service from the webservices runtime was not complete or did not exist.FBTSTM023EThe trust service did not start successfully because it could not locate the local or distributed configuration data.FBTSTM030EThe trust service did not fully stop.FBTSTM031EThe trust service did not fully start.FBTSTM032EThe trust service did not fully start, stop, or both.FBTSTM033EThe trust service failed to write configuration to persistent storage.FBTSTM034EThe context was not found.FBTSTM035EThe management method requested is not implemented.FBTSTM036EAn error occurred while retrieving the server's configuration for the management operation.FBTSTM038EA classname must be provided.FBTSTM039E The classname provided (classname) was not found in the server's classpath. FBTSTM041E The classname provided (classname) does not implement the required interface for modules. FBTSTM042E The classname provided (classname) does not implement the expected model. FBTSTM043E The given unique identifier (identifier) does not exist in the configuration. FBTSTM044EThe remove request could not be completed. There must be no references to the object being removed in order for the request to complete.FBTSTM046EThe unique identifier did not match the expected type.FBTSTM047EA unique identifier must be provided.FBTSTM048EThe request type is already in the configuration.FBTSTM049ETo add a request type, a request type URI must be provided.FBTSTM050EThe mapping type given is not a supported mapping type.FBTSTM051EThe request-type mapping requested to be modified does not exist.FBTSTM058E The chain (chain identifier) could not be initialized due to errors. FBTSTM059E The request failed to process successfully. FBTSTM060E The module reference ID used in the configuration of module chain ID 'chainId', (chainReference) is not valid. The module reference does not exist. FBTSTM061E The module reference used in the configuration of module chain ID 'chainId', (referenceId) is not valid. The module does not exist. FBTSTM062E The class 'className' referenced in module chain ID 'chainId' could not be initialized. The init method did not successfully complete. FBTSTM063E The module chain with ID 'id' could not be created because of an earlier error. FBTSTM064E The module chain with ID 'id' does not exist. FBTSTM065E The input request did not contain any data and cannot be processed. FBTSTM067E The module chain mapping with ID 'id' references a group that does not exist. FBTSTM068W The server encountered an exception while processing a request in validate mode. If the environment has trace enabled, the exception will appear in the trace log. FBTSTM069E The security token service could not create a logger in the given directory (directory name) because it is not a directory. FBTSTM070E The security token service message logger encountered an error and could not log the message. FBTSTM071E The security token service message logger encountered an error while creating the log file. The error text is: file name. FBTSTM072E The security token service message for chain mapping (Mapping) failed signature validation. FBTSTM073E The security token service is configured to validate signatures for chain mapping (Mapping) but the request received was not signed. FBTSTS021EThe Keystore service is not available for signing or validating assertions.FBTSTS310E The contents of the JWT could not be parsed as valid JSON. FBTSTS311E An error occured when performing an operation on the JWT. FBTSTS312E The signature of the JWT was not valid. FBTSTS313E The payload of the JWT could not be decrypted. FBTSTS314E The JWT algorithm provided was unknown or invalid. FBTSTS315E The header portion of the JWT was not valid. FBTSTS316E A 'none' signed JWT was provided, when there was a signature or information to perform signature validation present. FBTSTS317E The JWT was empty. FBTSTS318E The token payload contained the wrong type. The type [attributeName] was provided, when [attributeName] was expected. FBTSTS319E The request did not contain a JWT token. FBTSTS320E The claim [attributeName] did not match the configured value. FBTSTS321E The JWT presented has expired. FBTSTS322E The JWT presented is not yet considered valid. FBTSTS323E A JWT could not be formed. Parent topic: Error messages