firewalld config timeout when not using YaST

Anyone else experience this:

If I run firewalld from YaST I can configure for quite a while without having to re-enter the root credentials.

If I run firewalld from the KDE menu eventually firewalld will prompt me twice for the root password.

It is not a big deal. Just wondering if anyone else has observed this behavior.

Could you please explain?
I can start-stop, enable-disable the firewalld daemon from YaST Service Manager, but cannot configure the firewall from YaST.
From a KDE application launcher I can start firewall-config (via kdesu), but cannot run firewalld.

YaST > Security and Users > Firewall should launch the graphical firewall-config utility (if firewalld is already active).

So it does, but only with graphical YaST. I normally use the ncurses version, which displays:

Error
YaST currently does not have a module for configuring firewall. Please, 
either use "firewall-config" to configure your firewall via a user interface
or "firewall-cmd" for the command line.

Right ,there is no ncurses utility at this time, and even the graphical utility is not a YaST module. It’s a firewalld utility called by YaST. However, Red Hat/Fedora have system-config-firewall-tui (ncurses utility for firewalld), which might be a good option for openSUSE IMHO…

https://www.techrepublic.com/article/how-to-easily-manage-centos-firewalld-with-an-ncurses-tool/

Thanks, I had a quick look at system-config-firewall-tui (which I had been unaware of).
It seemed less onerous than reading the firewall-cmd man page, but I think that editing “/etc/firewalld/zones/public.xml” with vim (or whatever editor is preferred) is much simpler; that (plus scp) is how I converted our servers from SuSEfirewall2 to firewalld.