The Security1.0 catalog contains messages in the range
BEA097500 - BEA098499. Messages in this catalog are part of the
com.bea.common.security.internal.service
Internationalization package and the com.bea.common.security.internal.service Localization package.
|
BEA-097500
|
Error: method requires a config to be supplied for configuration but it wasnt supplied
|
Description
| The configuration supplied to method is incorrect |
|
Cause
| The configuration supplied to method is incorrect |
|
Action
| Verify the configuration supplied for method is correct |
|
|
BEA-097501
|
Error: config supplied to method is missing expected
|
Description
| The configuration supplied to method is incorrect |
|
Cause
| The configuration supplied to method is incorrect |
|
Action
| Verify the configuration supplied for method is correct |
|
|
BEA-097502
|
Error: MaxIdentitiesInCache value for the IdentityCacheService is invalid value
|
Description
| MaxIdentitiesInCache value for the IdentityCacheService is invalid value |
|
Cause
| MaxIdentitiesInCache value for the IdentityCacheService is invalid value |
|
Action
| Fix the MaxIdentitiesInCache |
|
|
BEA-097503
|
Error: The configured CertPathBuilder service returned a non X.509 cert path
|
Description
| The configured CertPathBuilder service returned a non X.509 cert path |
|
Cause
| The configured CertPathBuilder service returned a non X.509 cert path |
|
Action
| Correct the configured CertPathBuilder service |
|
|
BEA-097504
|
Error: AdjudicationService does not have an AdjudicatorV2Name but has multiple AccessDecision providers
|
Description
| AdjudicationService does not have an AdjudicatorV2Name but has multiple AccessDecision providers |
|
Cause
| AdjudicationService does not have an AdjudicatorV2Name but has multiple AccessDecision providers |
|
Action
| Correct the configuration |
|
|
BEA-097505
|
Error: None of the configured providerType support JAAS login
|
Description
| None of the configured providerType support JAAS login |
|
Cause
| None of the configured providerType support JAAS login |
|
Action
| Correct the configuration |
|
|
BEA-097506
|
Error: An AuthorizationProvider returned a null AccessDecision
|
Description
| An AuthorizatonProvider was not able to return an AccessDecision. |
|
Cause
| This should never happen. |
|
Action
| The AuthorizationProvider should be examined. |
|
|
BEA-097507
|
Error: arg0 may only be called if hasChallengeIdentityCompleted returns false
|
Description
| TBD |
|
Cause
| This should never happen. |
|
Action
| Contact BEA Support. |
|
|
BEA-097508
|
Error: arg0 may only be called if hasChallengeIdentityCompleted returns true
|
Description
| TBD |
|
Cause
| This should never happen. |
|
Action
| Contact BEA Support. |
|
|
BEA-097509
|
Error: arg0 returned a null arg1.
|
Description
| There is a configuration problem because a null object was returned. |
|
Cause
| This should never happen. |
|
Action
| Examine the specific objects referenced in the error message to see what may be the cause. |
|
|
BEA-097510
|
Error: Got back a null arg0 object.
|
Description
| There is a configuration problem because a null object was returned. |
|
Cause
| This should never happen. |
|
Action
| Examine the specific object referenced in the error message to see what may be the cause. |
|
|
BEA-097511
|
Error: Expected a arg0 object but did not get one.
|
Description
| There is a configuration problem because an object was expected and a different object was returned. |
|
Cause
| Possible configuration problem. |
|
Action
| Check configuration. |
|
|
BEA-097512
|
Error: Multiple challenges not supported.
|
Description
| Multiple challenges are not supported by ChallengeIdentityAsserter (v1) providers. |
|
Cause
| An attempt has made to handle multiple challenges with a provider that does not support it. |
|
Action
| Correct the code or configure a ChallengeIdentityAsserter that supports multiple challenges. |
|
|
BEA-097513
|
Error: Incorrect Cert Path type, expecting a arg0 type.
|
Description
| The wrong type of Cert Path was passed. |
|
Cause
| Incorrect code. |
|
Action
| TBD |
|
|
BEA-097514
|
Error: Multiple arg0 support the token type arg1
|
Description
| Only one can support the specified token type. |
|
Cause
| Incorrect configuration |
|
Action
| Remove from the configuration one of the objects supporting the token type |
|
|
BEA-097515
|
Error: Unsupported token type arg0
|
Description
| No objects are configured to support the specified token type. |
|
Cause
| Incorrect configuration |
|
Action
| Configure an object that supports the token type. |
|
|
BEA-097516
|
Error: Unable to validate a non X.509 cert path
|
Description
| Unable to validate a non X.509 cert path |
|
Cause
| Ensure that all cert paths are of type X.509 |
|
Action
| TBD |
|
|
BEA-097517
|
Error: A certificate is self signed but it is not the last certificate in the chain, see arg0
|
Description
| A certificate cannot be self signed unless it is the only certificate in the chain. |
|
Cause
| There is a certificate chain but one of the certificates is self signed. |
|
Action
| Ensure that the certificate chain is correct |
|
|
BEA-097518
|
Error: Issue DN mismatch error. Issued: arg0 does not match issuer: arg1.
|
Description
| The issuer DN of a certificate did not match the subject DN of the next certificate in the chain. |
|
Cause
| Inconsistent certificate chain. |
|
Action
| Ensure that the certificates in the chain correctly refer to each other. |
|
|
BEA-097519
|
Error: Certificate not signed by issuer. Certificate: arg0 not signed by issuer: arg1.
|
Description
| A certificate was not signed by the next certificate in the chain. |
|
Cause
| Inconsistent certificate chain. |
|
Action
| Ensure that the certificates in the chain correctly refer to each other. |
|
|
BEA-097520
|
Error: Capacity arg0 greater than maximum arg1
|
Description
| The specified queue capacity is greater than the allowed maximum. |
|
Cause
| Too large a queue capacity specified. |
|
Action
| Reduce the specified capacity. |
|
|
BEA-097521
|
Error: Maximum capacity arg0 is greater than the allowed arg1
|
Description
| The specified maximum queue capacity is larger than allowed. |
|
Cause
| Too large a queue capacity specified. |
|
Action
| Reduce the specified maximum capacity. |
|
|
BEA-097522
|
Error: Initial specified capacity of arg0 is illegal.
|
Description
| The specified capacity is illegal. |
|
Cause
| Incorrect capacity specified. |
|
Action
| Specify a correct capacity. |
|
|
BEA-097523
|
Error: Illegal load factor.
|
Description
| The specified load factor is not greater than 0 and less than 1. |
|
Cause
| An illegal load factor was specified. |
|
Action
| Specify a load factor greater than 0 and less than 1. |
|
|
BEA-097524
|
Error: No appropriate registered configuration to handle the AppConfigurationEntry named: arg0
|
Description
| No JAASConfiguration was registered that can handle the AppConfigurationEntry. |
|
Cause
| No appropriate JAASConfiguration has been registered. |
|
Action
| Register the appropriate JAASConfiguration |
|
|
BEA-097525
|
Error: Null JAASConfiguration.
|
Description
| Cannot register a null JAASConfiguration. |
|
Cause
| An attempt was made to register a null JAASConfiguration. |
|
Action
| Register a non-null JAASConfiguration |
|
|
BEA-097526
|
Error: Duplicate JAASConfiguration.
|
Description
| The JAASConfiguration has already been registered. |
|
Cause
| An attempt was made to register a JAASConfiguration twice. |
|
Action
| Do not attempt to register the JAASConfiguration twice. |
|
|
BEA-097527
|
Error: JAASConfiguration not registered.
|
Description
| Cannot unregister a JAASConfiguration that has not been registered. |
|
Cause
| An attempt was made to unregister a JAASConfiguration that is not registered. |
|
Action
| Do not attempt to unregister an unregistered JAASConfiguration. |
|
|
BEA-097528
|
Error: A null arg0 was specified.
|
Description
| A null method argument was specified. |
|
Cause
| This method cannot accept a null argument. |
|
Action
| Do not pass in a null argument. |
|
|
BEA-097529
|
Error: The principal validators arg0 and arg1 both validate the same principal types
|
Description
| There can only be one principal validator for each principal type |
|
Cause
| There can only be one principal validator for each principal type |
|
Action
| Correct the configuration |
|
|
BEA-097530
|
Error: No arg1 found in method arg0
|
Description
| No objects were found |
|
Cause
| Objects should have been configured and were not |
|
Action
| Correct the configuration |
|
|
BEA-097531
|
Error: Method arg0 was unable to sign a principal
|
Description
| There was a problem signing a principal |
|
Cause
| Something was wrong with the principal or the principal validator was incorrect |
|
Action
| Correct the configuration |
|
|
BEA-097532
|
Error: Null parameter supplied to method arg0
|
Description
| A null parameter was supplied to the method |
|
Cause
| A parameter was not correctly specified |
|
Action
| This is most likely a coding error. |
|
|
BEA-097533
|
Error: SecurityProvider service class name for arg0 is not specified.
|
Description
| There is a configuration problem because SecurityProviderConfig does not contain SecurityProvider service class name. |
|
Cause
| This should never happen. |
|
Action
| Examine the specific objects referenced in the error message to see what may be the cause. |
|
|
BEA-097534
|
Error: Failed to obtain an instance of class arg0.
|
Description
| There is a configuration problem because instantiation of arg0 has failed. |
|
Cause
| Possible configuration problem. arg0 class name is ivalid, or is not in the class path. It does not have a public no argment constructor, or has the constructor which failed to exectute. |
|
Action
| Check configuration. |
|
|
BEA-097535
|
Error: The configuration does not define a store, but providers that require a store are in use
|
Description
| The configuration does not define a store, but providers that require a store are in use |
|
Cause
| The configuration does not define a store, but providers that require a store are in use |
|
Action
| Configure a store service. |
|
|
BEA-097536
|
Error: The arg0 service can not be found for arg1
|
Description
| A particular service could not be found. |
|
Cause
| A null was returned when doing a service lookup |
|
Action
| Check the configuration to see that the missing service was actually configured. |
|
|
BEA-097537
|
Error: The setting setting supplied in the config configuration to method is invalid
|
Description
| The configuration setting setting supplied in config to method is incorrect |
|
Cause
| The configuration setting setting supplied in config to method is incorrect |
|
Action
| Verify the configuration supplied for method is correct |
|
|
BEA-097538
|
Error: The keystore storefile of type storetype could not be accessed
|
Description
| The keystore storefile of type storetype could not be accessed |
|
Cause
| The keystore storefile of type storetype could not be accessed and the configuration may be incorrect |
|
Action
| Verify the keystore storefile of type storetype can be accessed. |
|
|
BEA-097539
|
Error: Connection to the database is currently unavailable
|
Description
| Connection to the database is currently unavailable |
|
Cause
| Connection to the database is currently unavailable |
|
Action
| Verify the database configuration is correct and connectivity to the database |
|
|
BEA-097540
|
Warning: Property could not be parsed and will be skipped. Format must be name=value. Format found: property
|
Description
| Property could not be parsed and will be skipped. Format must be name=value. Format found: property |
|
Cause
| Property could not be parsed and will be skipped. Format must be name=value. Format found: property |
|
Action
| Check the format of the properties supplied to the configuration |
|
|
BEA-097541
|
Warning: method requires a needed, this was not available
|
Description
| method requires a needed, this was not available |
|
Cause
| This is most likely an internal coding error |
|
Action
| Check for configuration errors, if configuration appears valid contact BEA support |
|
|
BEA-097542
|
Error: Connection was not found by name name.
|
Description
| Connection was not found by name name. |
|
Cause
| This most like an internal error. |
|
Action
| Please check the log to see whether there is a connection pool checkout failure and find the cause. |
|
|
BEA-097543
|
Warning: Store service properties must not be null.
|
Description
| Store service properties must not be null. |
|
Cause
| This is most like a configuration error. |
|
Action
| Please check the Store service configuration. |
|
|
BEA-097544
|
Error: Get a null fieldName value in store service properties.
|
Description
| Get a null fieldName value in store service properties, Store service properties must specify a datastore connection fieldName. |
|
Cause
| This is most like a configuration error. |
|
Action
| Please check the Store service configuration. |
|
|
BEA-097545
|
Error: The internal state of the token is not consistent, possibly due to a failure during encoding/decoding the token.
|
Description
| The internal state of the token is not consistent, possibly due to a failure during encoding/decoding the token. |
|
Cause
| This most like an internal error. |
|
Action
| This most like an internal error. |
|
|
BEA-097546
|
Error: Timestamp is not of the correct length: arg0.
|
Description
| Timestamp is not of the correct length: arg0. |
|
Cause
| Timestamp format is not correct. |
|
Action
| Check the timestamp format. |
|
|
BEA-097547
|
Error: Timestamp contains illegal non-digit characters: arg0.
|
Description
| Timestamp contains illegal non-digit characters: arg0. |
|
Cause
| Timestamp format is not correct. |
|
Action
| Check the timestamp format. |
|
|
BEA-097548
|
Error: Timestamp has invalid timezone designator: arg0.
|
Description
| Timestamp has invalid timezone designator: arg0. |
|
Cause
| Timestamp format is not correct. |
|
Action
| Check the timestamp format. |
|
|
BEA-097549
|
Error: Timestamp is missing timezone designator: arg0.
|
Description
| Timestamp is missing timezone designator: arg0. |
|
Cause
| Timestamp format is not correct. |
|
Action
| Check the timestamp format. |
|
|
BEA-097550
|
Error: Month value is out-of-range for given year: arg0.
|
Description
| Month value is out-of-range for given year: arg0. |
|
Cause
| Timestamp format is not correct. |
|
Action
| Check the timestamp format. |
|
|
BEA-097551
|
Error: Day of month value is out-of-range for given month and year: arg0.
|
Description
| Day of month value is out-of-range for given month and year: arg0. |
|
Cause
| Timestamp format is not correct. |
|
Action
| Check the timestamp format. |
|
|
BEA-097552
|
Error: SPNEGO token trying to be constructed with invalid parsed information.
|
Description
| SPNEGO token trying to be constructed with invalid parsed information. |
|
Cause
| The parsed information is invalid. |
|
Action
| It's more like an internal error. |
|
|
BEA-097553
|
Error: SAMLSourceSite: Error while generating arg0: arg1.
|
Description
| SAMLSourceSite: Error while generating arg0: arg1. |
|
Cause
| Could not generate arg0. |
|
Action
| Its more like an internal error. |
|
|
BEA-097554
|
Error: Queries that test at least one scoping primary key must test all primary keys with a lower index.
|
Description
| Queries that test at least one scoping primary key must test all primary keys with a lower index. |
|
Cause
| Queries that test at least one scoping primary key must test all primary keys with a lower index. |
|
Action
| It's more like an internal error. |
|
|
BEA-097555
|
Error: This store does not support nested containers (e.g. collections of collections).
|
Description
| This store does not support nested containers (e.g. collections of collections). |
|
Cause
| This store does not support nested containers (e.g. collections of collections). |
|
Action
| It's more like an internal error. |
|
|
BEA-097556
|
Error: Primary key field must not be null: arg0.
|
Description
| Primary key field must not be null: arg0. |
|
Cause
| Primary key field must not be null: arg0. |
|
Action
| Check the query to see if the primary key is not null or empty. |
|
|
BEA-097557
|
Error: SAML V1 providers and V2 providers both configured.
|
Description
| SAML V1 providers and V2 providers both configured. |
|
Cause
| SAML V1 providers and V2 providers both configured. |
|
Action
| Check the configuration file for this error. |
|
|
BEA-097558
|
Error: FederationServicesMBean configuration Protocol Signing Key arg0 is invalid.
|
Description
| FederationServicesMBean configuration Protocol Signing Key arg0 is invalid. |
|
Cause
| FederationServicesMBean configuration Protocol Signing Key arg0 is invalid. |
|
Action
| Check the key information to see if its valid. |
|
|
BEA-097559
|
Error: FederationServicesMBean configuration SSL Client Key arg0 is invalid.
|
Description
| FederationServicesMBean configuration SSL Client Key arg0 is invalid. |
|
Cause
| FederationServicesMBean configuration SSL Client Key arg0 is invalid. |
|
Action
| Check the key information to see if its valid. |
|
|
BEA-097560
|
Error: Invalid Source Site configuration, arg0 must not be null or empty.
|
Description
| Invalid Source Site configuration, arg0 must not be null or empty. |
|
Cause
| Invalid Source Site configuration, arg0 must not be null or empty. |
|
Action
| Check the configuration to see if there is null or empty field. |
|
|
BEA-097561
|
Error: Store service is not initialized properly.
|
Description
| Store service is not initialized properly. |
|
Cause
| This is most like a configuration error. |
|
Action
| Please check the Store service configuration. |
|
|
BEA-097562
|
Error: Can't forward to custom post form, please check if the post form configuration is valid.
|
Description
| Can't forward to custom post form, please check if the post form configuration is valid. |
|
Cause
| The post form configuration is invalid. |
|
Action
| Please change the post form configuration. |
|
|
BEA-097563
|
Error: Connection was not found by name name.
|
Description
| Connection was not found by name name. |
|
Cause
| This problem can result from configuration or internal error. |
|
Action
| Please make sure that the specified data source is configured; also check the log to see whether there is a connection pool checkout failure and find the cause. |
|
|
BEA-097564
|
Error: The JDBC Connection Service initialization failed.
|
Description
| The SQL services JDBC depends upon are not configured properly or their service initialization failed. |
|
Cause
| Invalid or incorrect configuration. |
|
Action
| Please check that the SQL configuration has been specified properly. |
|
