andreas-ibm opened a new pull request, #28: URL: https://github.com/apache/axis-axis2-java-rampart/pull/28
`SymmetricBindingBuilder.setupEncryptedKey()` always generated an AES-128 session key (`KeyUtils.getKeyGenerator(WSConstants.AES_128)`), regardless of the encryption algorithm in the policy's `sp:AlgorithmSuite`. It now asks the policy's `AlgorithmSuite` for its encryption algorithm (`getEncryption()`), and falls back to AES-128 if that is null. Fixes https://issues.apache.org/jira/browse/RAMPART-462 - Only the key generator selection in `setupEncryptedKey()` changes. Error handling is unchanged (the existing `printStackTrace()` / `return null` on `WSSecurityException` is left as-is to keep this PR minimal). - For suites that already use AES-128 (e.g. `Basic128`) behaviour is identical. - For other suites (e.g. `Basic256`, `Basic192`, `TripleDes`) the generated key now matches the policy instead of being 128-bit AES. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
