The OSB Security catalog contains messages in the range
BEA386000 - BEA387099. Messages in this catalog are part of the
com.bea.wli.sb.messages
Internationalization package and the
com.bea.wli.sb.messages
Localization package.
BEA-386000
|
Error: Service Key Provider "provider" has a WSS X.509 Token credential and a Digital Signature credential, and they refer to different keys. WSS X.509 credentials have been deprecated. You must remove the WSS X.509 credential.
|
BEA-386001
|
Warning: Service Key Provider "provider" has a WSS X.509 Token credential and a Digital Signature credential and both refer to the same key. WSS X.509 credentials have been deprecated. You should remove the WSS X.509 credential.
|
BEA-386002
|
Warning: Authorization provider "provider" in the security realm is an instance of the DefaultAuthorizer (EntitleNet) provider. The DefaultAuthorizer provider has been deprecated in this Oracle Service Bus release. This provider will not be supported in a future release. Oracle recommends you use the XAML Authorization provider instead.
|
BEA-386003
|
Error: Mapped service account "ref" is invalid: user mapping entry for local user "localUsername" maps to non-existing remote user "remoteUsername"
|
BEA-386004
|
Error: Message-level access control denied access to proxy service proxy, operation operation, subject: subject
|
BEA-386005
|
Error: Mapped service account "ref" is invalid: its anonymous mapping maps to a non-existing remote user
|
BEA-386006
|
Alert: An error occurred while initializing name
|
BEA-386007
|
Alert: ResourceIdManager.registerResourceType() failed
|
BEA-386008
|
Error: Message level username/password authentication failed: reason
|
BEA-386009
|
Error: Message level custom token authentication failed: reason
|
BEA-386010
|
Error: Internal error: the proxy service is configured for message-level custom token or custom username/password authentication but WS-Security authentication has already taken place. WS-Security authentication and message-level custom authentication are mutually exclusive.
|
BEA-386011
|
Error: An error ocurred while evaluating the custom authentication token XPath selector: reason
|
BEA-386012
|
Error: An error ocurred while evaluating the message-level username XPath selector: reason
|
BEA-386013
|
Error: An error ocurred while evaluating the message-level password XPath selector: reason
|
BEA-386014
|
Error: the result of the XPath selector is empty
|
BEA-386015
|
Error: the XPath selector returned multiple nodes
|
BEA-386016
|
Error: the result of the XPath cannot be converted to java.lang.String (it is not a single text-node or attribute value)
|
BEA-386017
|
Error: the XPath cannot be evaluated because the request message does not have the required message part (part)
|
BEA-386018
|
Error: an error occurred while evaluating the XPath expression: errorMessage
|
BEA-386019
|
Error: The proxy service operation selection algorithm returned an invalid operation name: operation
|
BEA-386020
|
Error: the xpath result is not within the scope of the root node (rootNode), this can happen if the xpath uses the // construct. You must update your xpath to make sure it only selects elements within the root node (i.e. header or body).
|
BEA-386021
|
Error: No resource data
Description
| The resource data parameter was not supplied or is empty. |
Cause
| The resource data parameter was not supplied or is empty. |
Action
| Specify valid resource data. |
|
BEA-386022
|
Error: No resource type
Description
| The resource type information was not supplied. |
Cause
| The resource type information was not supplied. |
Action
| Specify a valid resource type. |
|
BEA-386023
|
Error: No resource identifier
Description
| The resource identifier parameter was not supplied or is empty. |
Cause
| The resource identifier parameter was not supplied or is empty. |
Action
| Specify a valid resource identifier. |
|
BEA-386024
|
Error: No resource keys found
Description
| No resource key information was supplied in the resource identifier. |
Cause
| An invalid resource identifier was supplied. |
Action
| Specify a valid resource identifier. |
|
BEA-386025
|
Error: Invalid data type for type resource key value
Description
| Invalid data type for type resource key value |
Cause
| The data type of a resource key value is not valid. |
Action
| Specify a valid resource key data type value. |
|
BEA-386026
|
Error: Invalid resource type: "type"
Description
| An invalid or unknown resource type was supplied. |
Cause
| An invalid or unknown resource type was supplied. |
Action
| Specify a valid resource type. |
|
BEA-386027
|
Error: Expected resource type: type
Description
| The resource type supplied did not match the expected type. |
Cause
| An invalid or unknown resource type was supplied. |
Action
| Verify a valid resource type was supplied and contact Oracle support. |
|
BEA-386028
|
Error: Expected resource key: key
Description
| The resource identifier supplied does not contain the expected key. |
Cause
| An invalid resource identifier was supplied. |
Action
| Specify a valid resource identifier. |
|
BEA-386029
|
Error: Unknown resource key: key
Description
| The resource key supplied in the resource data is unknown. |
Cause
| The resource key supplied in the resource data is unknown. |
Action
| Specify only resource keys valid for a specific resource type. |
|
BEA-386030
|
Error: Invalid application name
Description
| The application name parameter is not valid. |
Cause
| The application name parameter was empty or contains invalid values. |
Action
| Specify a valid application name. |
|
BEA-386031
|
Error: Invalid component name
Description
| The component name parameter is not valid. |
Cause
| The component name parameter was empty or contains invalid values. |
Action
| Specify a valid component name. |
|
BEA-386032
|
Error: Illegal application search name
Description
| The application name parameter is not valid. |
Cause
| The application name was not a legal search string. |
Action
| Specify a valid application name search string. |
|
BEA-386033
|
Error: Illegal component search name
Description
| The component name parameter is not valid. |
Cause
| The component name was not a legal search string. |
Action
| Specify a valid component name search string. |
|
BEA-386034
|
Error: No component type
Description
| The component type parameter is not valid. |
Cause
| The component type parameter is empty. |
Action
| Specify a valid component type of EJB, WebApp, Connector or WebService. |
|
BEA-386035
|
Error: Invalid component type: "type"
Description
| The component type parameter specified is not valid. |
Cause
| The component type parameter specified is not valid. |
Action
| Specify a valid component type of EJB, WebApp, Connector or WebService. |
|
BEA-386036
|
Error: Empty array value found
Description
| The array value supplied was empty. |
Cause
| An empty string was supplied for an array element of the resource key. |
Action
| Specify a valid string. |
|
BEA-386037
|
Error: Unexpected resource identifier data: "data"
Description
| The resource identifier supplied contains unexpected data. |
Cause
| An invalid resource identifier was supplied. |
Action
| Specify a valid resource identifier. |
|
BEA-386038
|
Error: Unexpected resource key array value: "value"
Description
| An unexpected value was supplied for a resource key array. |
Cause
| An invalid resource identifier was supplied. |
Action
| Specify a valid resource identifier. |
|
BEA-386039
|
Error: Empty type resource key string
Description
| Empty type resource key string. |
Cause
| An empty string was supplied for an element of the resource. |
Action
| Specify a valid string. |
|
BEA-386040
|
Error: Empty type resource key array string
Description
| Empty type resource key array string. |
Cause
| An empty string was supplied for an array element of the resource. |
Action
| Specify a valid string. |
|
BEA-386041
|
Error: key-pair binding with alias "alias" and purpose "purpose", but there is no such key-pair binding in the PKI Credential Mapper Provider in your security realm
Description
| In older release of ALSB (2.0 and 2.1), ALSB did not include the password to service key provider key-pair credentials in exported configuration jar files. When such a service key provider is later imported into subsequent releases, OSB expects the key-pair binding to already be present in the PKI Credential Mapper Provider. To do that, you would export the PKI Credential Mapper Provider data from your previous domain and import it into your new domain. NOTE: It is recommended that you instead re-configure this service key provider credentials, that way OSB will keep an encrypted copy of the key-pairs password and this error will not happen again |
Action
| Either import the PKI Credential Mapper provider data or reconfigure the service key providers credentials in the OSB console |
|
BEA-386042
|
Error: Mapped service account "svcacctRef" is invalid: the remote-user table is invalid, there are multiple entries with username "username"
Description
| The remote user table in a mapped service account cannot have multiple entries with the same username |
Action
| Edit the mapped service account and remove the duplicate entry |
|
BEA-386404
|
Notice: Key returned by KeyPairCredential is not a private key (it is not an instance of java.security.PrivateKey)
|
BEA-386405
|
Notice: Certificate returned by KeyPairCredential is not an X509 certificate (it is not an instance of java.security.cert.X509Certificate)
|
BEA-386406
|
Warning: unknown purpose purpose
|
BEA-386407
|
Info: An error occurred while trying to read trusted certificates from keystore keystore
|
BEA-386415
|
Error: Could not enforce access control policy: e
|
BEA-386417
|
Critical: Could not get the Authorization Manager
|
BEA-386800
|
Error: Could not find Authorization Provider $id
|
BEA-386801
|
Error: An error ocurred while activating access control changes for proxy "ref".
|
BEA-386802
|
Error: An error ocurred while removing access control policy from provider "autId" with resource id "resId".
|
BEA-386803
|
Error: An error ocurred while removing access control policy from provider "autId" for service "ref" at scope "scope".
|
BEA-386804
|
Error: An error ocurred while finding access control policy from provider "autId" with resource id "resId".
|
BEA-386805
|
Error: An error ocurred while finding access control policy from provider autId for service ref at scope scope.
|
BEA-386806
|
Error: An error ocurred while adding access control policy to provider "autId" with resource id "resId".
|
BEA-386807
|
Error: An error ocurred while adding access control policy to provider "autId" for service "ref" at scope "scope".
|
BEA-386808
|
Error: An error ocurred while setting access control policy expression on provider "autId" with resource id "resId".
|
BEA-386809
|
Error: An error ocurred while setting access control policy expression on provider "autId" for service "ref" at scope "scope".
|
BEA-386810
|
Error: Policy for resource id "resId" already exists in provider "autId".
|
BEA-386820
|
Error: Argument "ref" has an invalid value "operation".
|
BEA-386825
|
Notice: Access control policies for service "ref" will be upgraded from version "fromVersion" to version "toVersion".
|
BEA-386826
|
Warning: An error ocurred while upgrading access control policies for service "ref" from version "fromVersion" to version "toVersion". The access control policies will not be upgraded.
|
BEA-386827
|
Notice: Access control policies for service "ref" will be imported.
|
BEA-386828
|
Warning: An error ocurred while importing access control policies for service "ref". The access control policies will not be imported.
|
BEA-386830
|
Error: Invalid access control policy expression "expression" for service "ref" at "scope" level for provider "provider".
|
BEA-386831
|
Error: Multiple policies found for provider "provider" for service "ref" at scope "scope".
|
BEA-386832
|
Error: Access control policy found for invalid operation "operation" for service "ref".
|
BEA-386833
|
Error: Multiple policy entry found for same operation "operation" for service "ref".
|
BEA-386834
|
Error: Access control policy found for non-existing provider "provider" in service "ref".
|
BEA-386835
|
Error: Access control policy found for non-existing operation "operation" in service "ref".
|
BEA-386836
|
Error: Unnecessary proxy wide message access control policy found for service "ref". Hint: The service is neither an active security intermediary nor has custom authentication enabled.
|
BEA-386837
|
Error: Unnecessary operation specific message access control policy found for operation "operation" on service "ref". Hint: The service is not WSDL based.
|
BEA-386838
|
Error: Unnecessary operation specific message access control policy found for service "ref". Hint: The service is neither an active security intermediary nor has custom authentication enabled.
|
BEA-386839
|
Error: Message level access control policy found for non-existing operation "operation" on service "ref".
|
BEA-386840
|
Error: Invalid authroization provider "id" found in service "ref" at "scope".
|
BEA-386841
|
Error: Authroization provider "id" does not exist.
Action
| Authorization provider does not exist. Please check the provider. |
|
BEA-387000
|
Error: Failed to initialize Authorization Helper
|
BEA-387001
|
Error: No Policy Editor available
|
BEA-387004
|
Error: Policy deployment for resource resource failed: e
|
BEA-387008
|
Error: Failed to get WssPolicyCtx from service serviceRef
|
BEA-387009
|
Error: Failed to convert message context to SOAPMessage
|
BEA-387010
|
Error: Failed to store new SOAPMessage in routers message context
|
BEA-387011
|
Error: Failed to get the effective request policy for operation operation for service serviceRef
|
BEA-387012
|
Error: Failed to get the effective response policy for operation operation for service serviceRef
|
BEA-387013
|
Error: Failed to get the endpoint URL for service serviceRef
|
BEA-387014
|
Error: The request could not be mapped to one of the operations exposed by the service
|
BEA-387015
|
Error: Failed to get the outbound operation name from the routers message context
|
BEA-387016
|
Error: There is no target operation set on the outbound endpoint, the operation must be set in order to fetch the appropiate policy, set the operation in the message context
|
BEA-387017
|
Notice: There is no auditor service available. Most likely there are no audit providers configured in realm.
|
BEA-387018
|
Alert: Unexpected ProviderNotFoundException while deleting user/password credentials for service account serviceAccountRef
|
BEA-387019
|
Alert: Unexpected ProviderNotFoundException while deleting PKI credentials for service key provider serviceProviderRef
|
BEA-387020
|
Warning: ContextHandler property "key" has wrong type; expected type: expected; actual type: actual
|
BEA-387021
|
Warning: MessageContext property "key" has wrong type; expected type: expected; actual type: actual
|
BEA-387022
|
Error: An error ocurred during web service security inbound request processing [error-code: code, message-id: messageId, proxy: proxy, operation: operation]\n--- Error message:\nmsg
|
BEA-387023
|
Error: An error ocurred during web service security inbound response processing [error-code: code, message-id: messageId, proxy: proxy, operation: operation]\n--- Error message:\nmsg
|
BEA-387024
|
Error: An error ocurred during web service security outbound request processing [error-code: code, message-id: messageId, proxy: proxy, target: target, operation: operation]\n--- Error message:\nmsg
|
BEA-387025
|
Error: An error ocurred during web service security outbound response processing [error-code: code, message-id: messageId, proxy: proxy, target: target, operation: operation]\n--- Error message:\nmsg
|
BEA-387026
|
Error: An internal web service security error ocurred [error-code: code, message-id: messageId, proxy: proxy, target: target, operation: operation]\n--- Error message:\nmsg
|
BEA-387027
|
Info: Message-level access control policy grants access to proxy "proxy", operation "operation", message-id: messageId, subject: subject.
|
BEA-387028
|
Error: Message-level access control policy denies access to proxy "proxy", operation "operation", message-id: messageId, subject: subject.
|
BEA-387029
|
Error: An error happened while incrementing monitoring counter "counter" [message-id: messageId, proxy: proxy, target: target, operation: operation]
|
BEA-387030
|
Critical: Cannot read SerializedMS.dat: an IOException was thrown while reading data from path.
|
BEA-387031
|
Critical: SerializedMS.dat error: version mismatch, path: path. The version of the SerializedMS.dat file is not the supported version. Got version got, expected version expected. Verify that the SerializedMS.dat file has not been corrupted.
|
BEA-387032
|
Critical: Error opening SerializedMS.dat: path. A FileNotFoundException was thrown while opening the input stream. Verify that the SerializedMS.dat file exists and is accessible. Read the exception text for more information on diagnosing the problem.
|
BEA-387033
|
Critical: Error closing SerializedMS.dat: path. An IOException was thrown on the close of the input stream while reading the SerializedMS.dat file. Verify that the SerializedMS.dat file is valid. Read the exception text for more information on diagnosing the problem.
|
BEA-387034
|
Error: Could not create temporary file for filename , .new, directoryPath
Description
| When creating a temporary file, an IOException was thrown by the File.createTempFile method. |
Cause
| An error occurred creating the temporary file. |
Action
| Verify the filename and directory. Read the exception text for more information on diagnosing the problem. |
|
BEA-387035
|
Error: Could not create temporary file for filename, .old, directoryPath
Description
| When creating a temporary file, an IOException was thrown by the File.createTempFile method and the temp file could not be created. |
Cause
| An error occurred creating the temporary file. |
Action
| Verify the filename and directory. Read the exception text for more information on diagnosing the problem. |
|
BEA-387036
|
Error: Could not clear temporary file filename
Description
| The temporary file could not be deleted. |
Cause
| The delete method returned false. |
Action
| Verify that the file can be deleted and is not locked by some other process. |
|
BEA-387037
|
Error: Could not rename fromFilename to toFileName
Description
| The temporary file could not be renamed. |
Cause
| The rename method returned false. |
Action
| Verify that the file can be renamed and is not locked by some other process. |
|
BEA-387038
|
Error: Could not delete filename
Description
| The temporary file could not be deleted. |
Cause
| The delete method returned false. |
Action
| Verify that the file can be deleted and is not locked by some other process. |
|
BEA-387039
|
Error: Error creating filename
Description
| When writing a file using a FileOutputStream, a FileNotFound exception was thrown. |
Cause
| Either the file does not exist, the file is a directory rather than a regular file, or the file cannot be opened for reading. |
Action
| Verify the filename. Read the exception text for more information on diagnosing the problem. |
|
BEA-387040
|
Error: Error writing to file filename
Description
| When writing a file using a FileOutputStream, an IOException was thrown. |
Cause
| An error occurred writing the file. |
Action
| Read the exception text for more information on diagnosing the problem. |
|
BEA-387041
|
Alert: There are more than one user password credential mapper providers configured in your security realm. Oracle Service Bus supports at most one user password credential mapper. OSB service account management will be disabled. Review your realm configuration and make sure there is at most one provider.
|
BEA-387042
|
Alert: There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.
|
BEA-387043
|
Alert: The user password credential mapper provider configured in your security realm does not implement UserPasswordCredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider that supports writes if you need OSB service account support.
|
BEA-387044
|
Error: Invalid service account serviceAccount: the service account does not have a name
|
BEA-387045
|
Error: Invalid service account serviceAccount: the service account does not have a type
|
BEA-387046
|
Error: Invalid service account type: t
|
BEA-387047
|
Error: Invalid static service account serviceAccount: the service account does not have a username/password
|
BEA-387048
|
Error: Invalid static service account serviceAccount: the username is null
|
BEA-387049
|
Error: Invalid static service account serviceAccount: the username is invalid
|
BEA-387050
|
Error: Invalid static service account serviceAccount: the password is null
|
BEA-387051
|
Error: Invalid static service account serviceAccount: the password is invalid
|
BEA-387052
|
Error: Invalid mapper service account serviceAccount: the service account does not have any user mapping entries or an anonyous mapping
|
BEA-387053
|
Error: Invalid mapper service account serviceAccount: local username in user mapping is null
|
BEA-387054
|
Error: Invalid mapper service account serviceAccount: local username is invalid
|
BEA-387055
|
Error: Invalid mapper service account serviceAccount: the map has an entry with a null remote username/password
|
BEA-387056
|
Error: Invalid mapper service account serviceAccount: the map has an entry with a null remote username
|
BEA-387057
|
Error: Invalid mapper service account serviceAccount: the map has an entry with an invalid remote username
|
BEA-387058
|
Error: Invalid mapper service account serviceAccount: the map has an entry with a null remote password
|
BEA-387059
|
Error: Invalid mapper service account serviceAccount: the map has an entry with an invalid remote password
|
BEA-387060
|
Error: Invalid mapper service account serviceAccount: the service account has an anonymous mapping but the remote username on the anonymous mapping is null
|
BEA-387061
|
Error: Invalid mapper service account serviceAccount: the service account has an anonymous mapping but the remote username on the anonymous mapping is invalid
|
BEA-387062
|
Error: Invalid mapper service account serviceAccount: the service account has an anonymous mapping but the remote password on the anonymous mapping is null
|
BEA-387063
|
Error: Invalid mapper service account serviceAccount: the service account has an anonymous mapping but the remote password on the anonymous mapping is invalid
|
BEA-387064
|
Notice: Service account ref will be upgraded from version fromVersion to version toVersion
|
BEA-387065
|
Warning: An error ocurred while upgrading service account ref from version fromVersion to version toVersion. The service account will not be upgraded.
|
BEA-387066
|
Error: An error ocurred while activating changes for service account ref.
|
BEA-387067
|
Alert: There are more than one PKI credential mapper providers configured in your security realm. Oracle Service Bus supports at most one PKI credential mapper. OSB service key provider management will be disabled. Review your realm configuration and make sure there is at most one PKI credential mapper provider.
|
BEA-387068
|
Alert: There is no PKI credential mapper provider configured in your security realm. Service key provider management will be disabled. Configure a PKI credential mapper provider if you need service provider support. This is typically the case if you have Oracle Service Bus proxy services with web service security enabled or outbound 2-way SSL connections.
|
BEA-387069
|
Alert: The PKI credential mapper provider configured in your security realm does not implement PKICredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service key provider management will be disabled. Configure a PKI credential mapper provider that supports writes if you need OSB service provider support. This is typically the case if you have OSB proxies with web service security enabled or outbound 2-way SSL connections.
|
BEA-387070
|
Notice: Service key provider ref will be upgraded from version fromVersion to version toVersion
|
BEA-387071
|
Warning: An error ocurred while upgrading service key provider ref from version fromVersion to version toVersion. The service key provider will not be upgraded.
|
BEA-387072
|
Critical: An error ocurred while persisting the changes for service key provider ref to credential mapping provider providerName. The PKI credentials associated with service providers are now in an inconsistent state. This requires immediate attention.
Description
| An attempt to perform these changes failed: [changeDescription]. |
Cause
| See the stacktrace for additional information. |
Action
| Contact your Oracle representative. |
|
BEA-387073
|
Error: Invalid service key provider serviceProvider: missing key-alias for credentialPurpose key
|
BEA-387074
|
Error: Invalid service key provider serviceProvider: invalid key-alias for credentialPurpose key
|
BEA-387075
|
Error: Invalid service key provider serviceProvider: missing key-password for credentialPurpose key
|
BEA-387076
|
Error: Invalid service key provider serviceProvider: invalid key-password for credentialPurpose key
|
BEA-387077
|
Error: Invalid 21 compatibility resource id in service key provider serviceProvider for credentialPurpose key: resId
|
BEA-387078
|
Error: Failed to bind key-pair credential for service key provider serviceProvider and purpose credentialPurpose: error
|
BEA-387079
|
Error: Failed to bind key-pair credential for service key provider serviceProvider for digital signature purposes: the certificate does not support digital signatures. Key-alias: keyAlias
|
BEA-387080
|
Error: Failed to bind key-pair credential for service key provider serviceProvider for encryption purposes: the certificate does not support encryption. Key-alias: keyAlias
|
BEA-387081
|
Error: Error in service key provider "serviceProvider": could not read a certificate under keystore alias "keyAlias" for purpose "credentialPurpose"
|
BEA-387082
|
Error: Proxy service access denied (proxy: proxy, subject: subject)
|
BEA-387083
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] looking for a policy bound to "resourceId21"
|
BEA-387084
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] looking for a policy bound to "resourceId25"
|
BEA-387085
|
Warning: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] Cannot read access control policies stored in authorization provider atzProvider because the provider does not implement weblogic.management.security.authorization.PolicyReaderMBean. OSB cannot check if there is an ALSB 2.1 access control policy bound to the proxy service. If there are 2.1 access control policies bound to this proxy service, you must migrate the policy using the authorization provider tools (if you have not already migrated it). \nThis is the ALSB 2.1 resource id: oldResourceId. \nThis is the ALSB 2.5 resource id: newResourceId.
|
BEA-387086
|
Warning: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] Cannot migrate access control policies stored in authorization provider atzProvider because the provider does not implement weblogic.management.security.authorization.PolicyEditorMBean. OSB has determined there is an ALSB 2.1 access control policy bound to the proxy service. You must migrate this policy using the authorization provider tools (if you have not already done it). \nThis is the ALSB 2.1 resource id: oldResourceId. \nThis is the ALSB 2.5 resource id: newResourceId. \nThis is the ALSB 2.1 policy: policy.
|
BEA-387087
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] There is no policy bound to the 2.1 resource (resource21) or 2.5 resource (resource25).
|
BEA-387088
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] There is no policy bound to the 2.1 resource (resource21) but there is already a policy bound to the 2.5 resource (resource25). The 2.5 policy will be preserved.\n This is the policy:\n policy25
|
BEA-387089
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] There is a policy bound to the 2.1 resource (resource21) AND a policy bound to the new 2.5 resource (resource25). The 2.1 policy will overwrite the 2.5 policy.\n This is the 2.1 policy:\n policy21 \nThis is the 2.5 policy:\n policy25
|
BEA-387090
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] Deleting the policy bound to the 2.1 resource (resourceId).
|
BEA-387091
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] An error occurred while deleting the policy bound to "resource". See the exception for more details.
|
BEA-387092
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] Deleting the policy bound to the 2.5 resource (resourceId).
|
BEA-387093
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] An error occurred while deleting 2.5 policy. See the exception for more details.
|
BEA-387094
|
Info: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] An error occurred while binding the policy against the 2.5 resource. See the exception for more details.
|
BEA-387095
|
Alert: [Policy Migration] [proxy service: proxy] [authorization provider: atzProvider] The 2.1 policy cannot be migrated because it makes use of policy predicates which are specific to URLResource. A deny-all policy will be bound to the proxy. You must re-configure this policy in the console.
|
BEA-387096
|
Alert: Oracle Service Bus could not determine if the default ALSBProxyServiceResource policy is present or not because some authorization providers do not implement PolicyReaderMBean. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. If the policy is indeed missing, the administrator must create it.
|
BEA-387097
|
Critical: Oracle Service Bus has determined the default ALSBProxyServiceResource policy is missing. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. Access to all OSB proxy services will be denied. The administrator must create the policy using the provider tools.
|
BEA-387098
|
Notice: Deployed new out-of-the-box Oracle Service Bus access control policy; authorization provider: "provider", resource-id: "resourceId", policy: "policy".
|
BEA-387099
|
Error: Service Key Provider "provider" has a WSS X.509 Token credential. WSS X.509 credentials have been deprecated. You must configure a Digital Signature credential instead.
|