Caideyipi opened a new pull request, #18021:
URL: https://github.com/apache/iotdb/pull/18021

   ## Description
   Pipe/config snapshot user sync may replay `CreateUserWithRawPassword`, where 
the password field is already the stored raw/encrypted password value from the 
source cluster. When the receiver has `enforce_strong_password=true`, comparing 
that raw stored value with the username can reject legacy users such as 
`legacyuser/legacyuser`, causing repeated `Failed to handleTransferConfigPlan` 
errors.
   
   This change keeps normal `CreateUser` strong-password checks unchanged, but 
skips the username/password equality check for raw-password replay paths where 
`enableEncrypt=false`. Username validation is still preserved.
   
   ## Tests
   - `mvn spotless:apply -pl iotdb-core/confignode,iotdb-core/node-commons`
   - `git diff --check`
   - Attempted `mvn -pl iotdb-core/confignode -am 
"-Dtest=AuthorInfoTest#createUserWithRawPassword" "-DfailIfNoTests=false" 
"-Dsurefire.failIfNoSpecifiedTests=false" test`, but the local JVM crashed 
during `node-commons` compilation with native memory allocation failure 
(`hs_err_pid9412.log` generated and removed).
   


-- 
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]

Reply via email to