The WLSS.Security1.0 catalog contains messages in the range
BEA330200 - BEA330399. Messages in this catalog are part of the
com.bea.wcp.sip.i18n
Internationalization package and the com.bea.wcp.sip.i18n Localization package.
|
BEA-330200
|
Debug: Registering trusted host for category: host, address: address
|
Description
| Registering trusted host for category: host, address: address |
|
Cause
| Registering trusted hosts. The category is either "SecurityManagerFilter" (configured as the init-param of the filter) or "P-Asserted-Identity" (configured in the PAssertedIdentityAsserterProvider). |
|
Action
| This is an informational message for debug purposes only, and no action is required. This message is logged during application deployment when debugging is enabled for the debug category wlss.security. |
|
|
BEA-330201
|
Debug: Registering trusted host for category with wildcard : host
|
Description
| Registering trusted host for category with wildcard : host |
|
Cause
| Registering trusted host with wildcard. The category is either "SecurityManagerFilter" (configured as the init-param of the filter) or "P-Asserted-Identity" (configured in the PAssertedIdentityAsserterProvider). |
|
Action
| This is an informational message for debug purposes only, and no action is required. This message is logged during applicaiton deployment when debugging is enabled for the debug category wlss.security. |
|
|
BEA-330202
|
Error: The trusted-host parameter for category with value: host is not valid.
|
Description
| The trusted-host parameter for category with value: host is not valid. |
|
Cause
| Failed to resolve the host name assigned to the trusted host parameter. The category is either "SecurityManagerFilter" (configured as the init-param of the filter) or "P-Asserted-Identity" (configured in the PAssertedIdentityAsserterProvider). |
|
Action
| To fix this correct the sipserver.xml or PAssertedIdentityAsserter provider as applicable. |
|
|
BEA-330203
|
Debug: The remote InetAddress could not be resolved, failed with UnknownHostException for host
|
Description
| The remote InetAddress could not be resolved, failed with UnknownHostException for host |
|
Cause
| The remote address of the incoming request was not recognized. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-330204
|
Error: Could not deploy role: role for SIP webapp: webapp application: app.
|
Description
| Could not deploy role: role for SIP webapp: webapp application: app. |
|
Cause
| The SIP application could not deploy the role defined in sip.xml. |
|
Action
| Make sure that security is configured properly in the server. Also examine the stack trace for the exact cause of the problem. |
|
|
BEA-330205
|
Warning: In SIP app: webapp, the str1: roles defined in sip.xml str2 not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.
|
Description
| In SIP app: webapp, the str1: roles defined in sip.xml str2 not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name. |
|
Cause
| A mapping of the role to a principal name was not found in a security-role-assignment in weblogic.xml. |
|
Action
| Because the server will use an implicit role mapping, make sure that the principal-name is the one you intend to use. |
|
|
BEA-330206
|
Error: Could not deploy the security policy for the resource: resource against the security-constraint defined in sip.xml
|
Description
| Could not deploy the security policy for the resource: resource against the security-constraint defined in sip.xml |
|
Cause
| The SIP application failed to deploy the policy for the security-constraint defined in sip.xml. |
|
Action
| Make sure that security is configured properly in the server. Also examine the stack trace for the exact cause of the problem. |
|
|
BEA-330207
|
Error: Failed to undepoy security policy for resource: resource while undeploying SIP application.
|
Description
| Failed to undepoy security policy for resource: resource while undeploying SIP application. |
|
Cause
| The security policy defined in sip.xml failed to undeploy upon SIP application undeployment. |
|
Action
| Check the exception for the exact cause of the problem. |
|
|
BEA-330208
|
Error: Failed to undepoy security policy for resource: resource while undeploying the SIP application.
|
Description
| Failed to undepoy security policy for resource: resource while undeploying the SIP application. |
|
Cause
| The security role defined in sip.xml failed to undeploy upon SIP application undeployment. |
|
Action
| Check the exception for the exact cause of the problem. |
|
|
BEA-330209
|
Warning: In SIP app: webapp, the method role: rolename defined in the descriptor: file does not map to a run-as-identity principal in security-role-assignment in weblogic.xml. Will use the first principal-name: principal in security-role-assignment as the run-as-identity.
|
Description
| In SIP app: webapp, the method role: rolename defined in the descriptor: file does not map to a run-as-identity principal in security-role-assignment in weblogic.xml. Will use the first principal-name: principal in security-role-assignment as the run-as-identity. |
|
Cause
| A mapping of the runAs role to a run-as-identity principal in a security-role-assignment was not found in weblogic.xml. |
|
Action
| Because the server has decided to use an implicit mapping, make sure that the principal-name is one you intended to use. |
|
|
BEA-330210
|
Warning: SIP app: webapp, run-as role: rolename defined in sip.xml has not been mapped to a run-as-identity principal in security-role-assignment in weblogic.xml. Also there is no security-role-assignment defined for this role. Will use the rolename itself as a principal-name for rolename for the servlet.
|
Description
| SIP app: webapp, run-as role: rolename defined in sip.xml has not been mapped to a run-as-identity principal in security-role-assignment in weblogic.xml. Also there is no security-role-assignment defined for this role. Will use the rolename itself as a principal-name for rolename for the servlet. |
|
Cause
| A mapping for the run-as role to a run-as-identity principal was not found in a in security-role-assignment in weblogic.xml. |
|
Action
| Because the server has decided to use an implicit mapping, make sure that the principal-name is the one you intended to use. |
|
|
BEA-330211
|
Error: The run-as user: user for the servlet: servlet for the SIP application: webapp could not be resolved to a valid user in the system. Verify the user exists.
|
Description
| The run-as user: user for the servlet: servlet for the SIP application: webapp could not be resolved to a valid user in the system. Verify the user exists. |
|
Cause
| The run-as element in sip.xml, or its mapping in weblogic.xml, refers to an invalid user. |
|
Action
| Verify that the user exists. |
|
|
BEA-330212
|
Debug: The servlet being accessed by the SIP request: req requires TLS. Denying permission.
|
Description
| The servlet being accessed by the SIP request: req requires TLS. Denying permission. |
|
Cause
| A SIPS request was expected, rather than a SIP request. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-330213
|
Debug: message
|
Description
| message |
|
Cause
| This is a general-purpose debug message. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-330214
|
Debug: message
|
Description
| message |
|
Cause
| This is a general-purpose debug message, with stack trace. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-330215
|
Error: Failed while querying PAssertedIdentityAsserterMBean for trusted-hosts configuration.
|
Description
| Failed while querying PAssertedIdentityAsserterMBean for trusted-hosts configuration. |
|
Cause
| This is an unexpected exception. |
|
Action
| Check your CLASSPATH and make sure that you are running the server with the correct version. |
|
|
BEA-330216
|
Error: webapp: The sip.xml has auth-method="DIGEST", but no DIGEST IdentityAssertion Providers have been configured.
|
Description
| webapp: The sip.xml has auth-method="DIGEST", but no DIGEST IdentityAssertion Providers have been configured. |
|
Cause
| You must configure a DIGEST IdentityAssertion provider in order to use DIGEST authentication. |
|
Action
| WebLogic SIP Server ships with LDAP and DBMS-based IdentityAssertion providers. Refer to the documentation to configure a provider. |
|
|
BEA-330217
|
Warning: In SIP app: webapp, the role: role defined in sip.xml has not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.
|
Description
| In SIP app: webapp, the role: role defined in sip.xml has not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name. |
|
Cause
| A mapping of the role to a principal name was not found in a security-role-assignment in weblogic.xml. |
|
Action
| Because the server will use an implicit role mapping, make sure that the principal-name is the one you intend to use. |
|
|
BEA-330218
|
Warning: In SIP app: webapp, the roles: role defined in sip.xml have been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.
|
Description
| In SIP app: webapp, the roles: role defined in sip.xml have been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name. |
|
Cause
| A mapping of the role to a principal name was not found in a security-role-assignment in weblogic.xml. |
|
Action
| Because the server will use an implicit role mapping, make sure that the principal-name is the one you intend to use. |
|
|
BEA-330219
|
Warning: In SIP app: webapp, the method role: rolename defined in the descriptor: file does not map to a run-as-identity principal in a security-role-assignment element in weblogic.xml. Will use the first principal-name: principal in security-role-assignment as the run-as-identity defined at the application level (weblogic-application.xml).
|
Description
| In SIP app: webapp, the method role: rolename defined in the descriptor: file does not map to a run-as-identity principal in a security-role-assignment element in weblogic.xml. Will use the first principal-name: principal in security-role-assignment as the run-as-identity defined at the application level (weblogic-application.xml). |
|
Cause
| A mapping of the runAs role to a run-as-identity principal in a security-role-assignment was not found in weblogic.xml. |
|
Action
| Because the server has decided to use an implicit mapping, make sure that the principal-name is one you intended to use. |
|
|
BEA-330220
|
Error: In SIP app: webapp, the method role: rolename defined in the descriptor: file has not been mapped to a run-as-principal-name in weblogic.xml. To fix this, define a mapping in weblogic.xml using the servlet-descriptor/run-as-principal-name or run-as-role-assignment. Alternatively, change the security-model for the application to Advanced and the combined-role-mapping flag in the RealmMBean to false.
|
Description
| In SIP app: webapp, the method role: rolename defined in the descriptor: file has not been mapped to a run-as-principal-name in weblogic.xml. To fix this, define a mapping in weblogic.xml using the servlet-descriptor/run-as-principal-name or run-as-role-assignment. Alternatively, change the security-model for the application to Advanced and the combined-role-mapping flag in the RealmMBean to false. |
|
Cause
| By default unmapped role-mappings are not allowed for the sip/web applications. |
|
Action
| To fix this you will need to define a mapping in weblogic.xml/weblogic-application.xml. Alternatively, use a different security model (Advanced) and also disable combined-role-mapping flag for the RealmMBean. This setting allows WLS 8.x style of role mappings. |
|
