Skip to content

rabbitmq jasypt encryption update#669

Open
DaanHoogland wants to merge 1 commit into
apache:4.22from
shapeblue:ghi13352-rabbitmqEncryption
Open

rabbitmq jasypt encryption update#669
DaanHoogland wants to merge 1 commit into
apache:4.22from
shapeblue:ghi13352-rabbitmqEncryption

Conversation

@DaanHoogland

@DaanHoogland DaanHoogland commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

@DaanHoogland
DaanHoogland force-pushed the ghi13352-rabbitmqEncryption branch from 4132455 to f2fc387 Compare July 23, 2026 09:25
Comment on lines +169 to +178
.. note::
Older versions of this guide referenced
``org.jasypt.spring3.properties.EncryptablePropertyPlaceholderConfigurer``, which comes
from the ``jasypt-spring3`` artifact. That artifact is not shipped with CloudStack and is
not compatible with the Spring 5 used since CloudStack 4.x, so beans referencing it fail
to load with a ``ClassNotFoundException``. Use
``com.cloud.utils.crypt.EncryptablePropertyPlaceholderConfigurer`` instead, which ships
with CloudStack and works the same way. This bean also expects encrypted values to be
wrapped as ``ENC(...)``, matching the convention used elsewhere in CloudStack.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this might not be needed

Suggested change
.. note::
Older versions of this guide referenced
``org.jasypt.spring3.properties.EncryptablePropertyPlaceholderConfigurer``, which comes
from the ``jasypt-spring3`` artifact. That artifact is not shipped with CloudStack and is
not compatible with the Spring 5 used since CloudStack 4.x, so beans referencing it fail
to load with a ``ClassNotFoundException``. Use
``com.cloud.utils.crypt.EncryptablePropertyPlaceholderConfigurer`` instead, which ships
with CloudStack and works the same way. This bean also expects encrypted values to be
wrapped as ``ENC(...)``, matching the convention used elsewhere in CloudStack.

Comment on lines +232 to +236
``PBEWithMD5AndDES``, used in earlier releases of this guide, is a weak algorithm and should
not be used for new deployments; ``PBEWITHHMACSHA512ANDAES_256`` above is a stronger,
future-proof alternative. Use the ``jasypt`` CLI tools (or any tool using the jasypt library)
with the same algorithm, IV generator and ``APP_ENCRYPTION_PASSWORD`` to produce the
encrypted values for ``cred.properties``.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
``PBEWithMD5AndDES``, used in earlier releases of this guide, is a weak algorithm and should
not be used for new deployments; ``PBEWITHHMACSHA512ANDAES_256`` above is a stronger,
future-proof alternative. Use the ``jasypt`` CLI tools (or any tool using the jasypt library)
with the same algorithm, IV generator and ``APP_ENCRYPTION_PASSWORD`` to produce the
encrypted values for ``cred.properties``.
``PBEWithMD5AndDES``, used in earlier releases of this guide, is a weak algorithm and should
At least ``PBEWITHHMACSHA512ANDAES_256`` or stronger algorithms should be used. Use the ``jasypt`` CLI tools (or any tool using the jasypt library)
with the same algorithm, IV generator and ``APP_ENCRYPTION_PASSWORD`` to produce the
encrypted values for ``cred.properties``.

@DaanHoogland DaanHoogland left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note; this was ai generated from the issue. I think we don’t need to point to older versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant