Users -> Expiration date

[JohnDoe17]

Hello.

I am running 26.4.2-amd64, and I've recently noticed that the "Expiration date" setting in the "System -> Access -> Users" page is not apparently doing anything.  I'm not sure when it stopped working, but I've experimented with setting an expiration date on two different accounts for two different days, recently, and neither of the accounts were disabled after the expiration date passed.

This feature has worked in the past, I'm just not exactly certain at what point it stopped working.

Thank you

[franco]

Hi,

What's your expectation of the feature?  If an account has expired, login is no longer possible.  This is only true for local accounts and API keys.  Externally managed users need to be disabled externally.


Cheers,
Franco

[JohnDoe17]

Thanks for the quick reply.

The two accounts I experimented with were local accounts.  In the past, when an account expired, it turned from blue to grey and when I viewed the account it showed "Disabled."  That is not happening anymore.  My expectation is that it worked the same way now.

[franco]

Well, yes, it has been decoupled from disabling the account. The expiration date is explicit enough. We can, however, consider showing the user as grey when expired, too?


Cheers,
Franco

[JohnDoe17]

Ahh, I didn't understand that a local account expiring due to "Expiration date" setting had been decoupled from "Disabled," so that clears up some of my confusion.  (And after doing a bit more research, I think understand why it was decoupled.)

However, from an administration point of view, it's handy to be able to quickly glance down the list of colored icons to see which local user accounts are actually still "active," so I would be in favor of greying out the icon when the account is Disabled or expired.

Thank you for the responses and your consideration of the icon color change.

I am a long-time user of OPNsense, and I think the team does a fantastic job with the product and its support!

[franco]

Hey,

Thanks for your support!

Here's a simple idea to solve this:

# opnsense-patch https://github.com/opnsense/core/commit/5423ae8fb8c


Cheers,
Franco