Release Notes › Known Issues › General Issues › SOA Security Manager Fails To Generate WS-Security Headers Using RSA-OAEP Encryption (70408)

Previous Topic: Authentication of Encrypyted Requests Intermittently Failing with Red Hat Policy Server (77348)

Next Topic: Responses Configured to Generate Signed SAML Session Tickets Using Public Key Obtained from XML Digital Signature Authentication Produce Unsigned SAML Session Tickets (98865)

SOA Security Manager Fails To Generate WS-Security Headers Using RSA-OAEP Encryption (70408)

SOA Security Manager fails to create an encrypted WS-Security token when a response is configured to use the RSA-OAEP algorithm to encrypt the symmetric encryption key, generating the following error in tmxmltoolkit.log:

008-05-22 14:53:10,531 [INFO] handler.response.WSSecurityUsernameResponseHandler 8A2ADA6E-3D9B-57FB-35E3-9CC05471E849 - Cannot do encryption: unsupported key algorithm provided: rsa_oaep

Workaround

Configure the WS-Security header generating response to use the default rsa-1_5 algorithm to encrypt the symmetric encryption key.

Copyright © 2009 CA. All rights reserved. Email CA about this topic