Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Implemented
-
Trunk
-
None
-
None
-
None
Description
As stated by comment, after upgrading Shiro to latest version, an EntityCrypto exception will be triggered when loading data.
After some investigation, I found that the default padding scheme of ECB mode in Shiro is different between v1.4.1 and v1.7.1, i.e.:
v1.4.1 getPaddingSchemeName() output: PKCS5Padding
v1.7.1 getPaddingSchemeName() output: NoPadding
After specifying padding scheme explicitly, EntityCrypto exception does not raise anymore.
I'll create a pull request in GitHub.
Attachments
Issue Links
- links to