WSM-00256: The property "Keystore Encryption Key Alias" is not set
(Doc ID 1580238.1)
Last updated on FEBRUARY 16, 2021
Applies to:Oracle Web Services Manager - Version 220.127.116.11.0 to 18.104.22.168.160517 [Release 11gR1 to 11g]
Information in this document applies to any platform.
In Fusion Middleware 11g, when trying to test a service that has an x509 v1.1 policy that uses a keystore with a key to encrypt and authenticate the message attached to it (oracle/wss11_x509_token_with_message_protection_client_policy on the client side, oracle/wss11_x509_token_with_message_protection_service_policy on the server side, the following error is received:
oracle.wsm.security.SecurityException: WSM-00256 :
The property "Keystore Encryption Key Alias" is not set. The csf map "oracle.wsm.security" found in the credential store is being used and the following keys are found in this map :- [sign-csf-key: serverkey], [enc-csf-key: serverkey], [keystore-csf-key: keystore-csf-key],
The properties found in the JPS config are :- [keystore.provider.type: file], [keystore.sig.csf.key: sign-csf-key], [keystore.csf.map: oracle.wsm.security]
The environment was originally set up to use version 1.0 of the policies (oracle/wss10_x509_token_with_message_protection_client_policy on the client side, oracle/wss10_x509_token_with_message_protection_service_policy on the server side) and the policies were changed without changing anything in the keystore being used, or in the credential store. The original configuration worked fine.
Is there something missing from the mapping configuration, is the configuration different somehow with the different policies?
In the environment. two keystores are being used, one for the server and one for the Client.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document