From 02a131f900adc9729782ab972168b3069357fefc Mon Sep 17 00:00:00 2001
From: jeffersoncasimir <15801528+jeffersoncasimir@users.noreply.github.com>
Date: Thu, 8 Jun 2023 11:54:54 -0400
Subject: [PATCH] [user_accounts] Update TestPlan.md

The pwned password example was not complex enough to pass the complexity check and trigger the pwned check.
---
 modules/user_accounts/test/TestPlan.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/user_accounts/test/TestPlan.md b/modules/user_accounts/test/TestPlan.md
index a40296a18f2..8083e718e51 100644
--- a/modules/user_accounts/test/TestPlan.md
+++ b/modules/user_accounts/test/TestPlan.md
@@ -61,7 +61,7 @@ When creating or editing a user: (subtest: edit_user)
     without saving any changes to the user profile.
 28. Check that if config setting 'Enable "Pwned Password" check' is set to 'Yes', then validation to make sure that the password
     entered (both for add user and edit user pages) has not been pwned is done. Also check that disabling this setting disables the 
-    validation. Example of a pwned password: AKAX89Wn
+    validation. Example of a pwned password: ji32k7au4a83
 29. Check that a 'Reject user' button will be available on the edit user page if the editee is a user whose account is awaiting approval and the editee
     has not yet logged in.
 30. Edit a user that fits the conditions listed above and reject it. Make sure that the user has been removed from the database and does not show up in