shiro.ini - already hashed passwords are not considered when automatic hashing through Account Manager functionality occurs

Current Situation
A password hash was generated with the CLI \shiro-tools-hasher\1.3.2> java -jar shiro-tools-hasher-1.3.2-cli.jar --algorithm SHA-512 -p as described in JOC-270.
Only one user got this password hash, all other users still had the clear text password.
Using Manage Accounts in JOC to update a current user results in all passwords for all users in shiro.ini were hashed afterwards.
The User with the already existing password hash cannot login anymore, because the already existing hash was presumed a password and hashed again.

Desired Behavior
When an Administrator creates a password hash with the CLI tool from shiro for one user, the automatic password hashing of the Manage Account function in JOC is not allowed to rehash the already exisitng password hash. It should recognize, that the already existing password hash is a hash and not a clear text password.