Flex 100HP - wrong "password changed date" value

GiuseppeR

Hello everyone,

I went for a walk among the settings of the new Zyxel family POE firewall and I noticed that the firewall tells me that yesterday (2024-10-10) I changed my password:

I never changed it since first installation (2024-10-04).

mMontana

At first installation date was correctly set?

In doubt… change it today, simply assure you that… date and time are correct before change the password.

If possibile, after a successful login, consider a reboot of the device.

Also consider verify that device is running latest firmware version.

Zyxel_Judy

Hi @GiuseppeR ,

In addition to mMontana's recommendation, you can also check the logs for any unusual login activity and change your password if needed.

GiuseppeR

Hello @Zyxel_Judy and @mMontana

the "Password Changed Date" value is influenced by the firmware update itself:

I could not change the password as suggested because it is shared with Zyxel engineering team, we are testing a new firmware with a firewall in production.

That "2024-10-25 19:59" is the timestamp of the latest update I installed from a local folder just some minutes ago.

I think that changing value should be considered a bug, because it is not really a "Password Changed Date". It could be misleading like it happened with this thread

mMontana

I cannot agree more.

Zyxel_Judy

Hi there,

We attempted to reproduce your issue by upgrading a USG FLEX 200H from firmware version 1.21 to 1.30. However, we were unable to replicate the problem - the Password Changed Date correctly showed the actual date/time of the password change, not the firmware upgrade date.

That "2024-10-25 19:59" is the timestamp of the latest update I installed from a local folder just some minutes ago.

To help us investigate further, please provide:

1. The original firmware version you upgraded from
2. The firmware version you upgraded to
3. The method you used for the firmware upgrade

GiuseppeR

Hello @Zyxel_Judy

please let me highlight that the firewall where I can see those effects is a USG FLEX 100HP and not a 200H.

Since the first installation I did not change the admin password.

It is shared with Zyxel engineering team for testing purposes.

At the beginning I installed the official fimware, then customized it to my needs, put it in production with a Wifi7 PoE access point.

Lately I did these steps:

• upgraded via on prem web UI to 1.21 official fw
• upgraded via Nebula APP to 1.30 official fw
• having a lot of issues with this update so reverting back (automatically made by the fw itself) to 1.21
• I had to reboot twice the 100 HP with 1.21 onboard because the firewall wanted to be rebooted because it told me it could not update its firmware
• upgraded via on prem web UI to V1.30(ACII.0)ITS-m6149 to test a fixing for general availability

I'm at your disposal, see you soon

Zyxel_Judy

HI @GiuseppeR ,

We have tested the following:

1. Used a USG FLEX 100HP
2. Upgraded from firmware version 1.21 (official) to 130ACII0ITS-24WK45-m6209
3. Confirmed that the Password Changed Date correctly shows the actual password change date/time, not the firmware upgrade date

Please check your Community inbox for firmware version 130ACII0ITS-24WK45-m6209 and verify if this resolves your issue.

GiuseppeR

Hello @Zyxel_Judy

I tried also on another H series firewall.

Some minutes ago I upgraded a 200H from 1.21 to 1.30P1 and the "password changed date" was modified as shown below:

You can see 2024-11-14 13:47 (timestamp for upgrading) while right now the time is 2024-11-14 14:00

GiuseppeR

Hello again @Zyxel_Judy

some minutes ago I tried also the same 1.21 to 1.30P1 upgrade with a 100HP:

As you can see the timestamp for "Password Changed Date" is 2024-11-14 14:36 while right now the time is 2024-11-14 14:47

Zyxel_Judy

Hi @GiuseppeR ,

Ive just upgraded my USG FLEX 200H from version 1.21 to 1.30P1 using the cloud upgrade method through the local GUI. However, the Password Changed Date still shows the time when I last modified the password, not the time of the firmware upgrade.

Could you please share your firmware upgrade process? This will help us reproduce the issue and provide further assistance.