Hello everyone!
I am experiencing some weird behaviour with login on Fortigate device with os 7.4.4 and 7.4.5.
I can successfully login on the device with whatever username (but no one local username, try for example username: qwerfdsa) as long as the password is correct (the password of a local user or from a tacacs+ server).
I discovered this by mistake
There is anyone who also discovered this problem?
And also, there is a way to solve this problem?
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi,
Maybe this is enabled?
config system global
set admin-restrict-local enable
end
The problem was a combination of stale HTTPS administration sessions, coupled with the disabling of "Allow concurrent sessions" in System>Settings>Administration Settings.
Hi,
I’ve checked the admin-restrict-local and it is disable.
Also I’ve checked the other post that you’ve sent me and the problem is still here.
I think this is a big problem for Fortinet devices with this to version of OS
Hi @Forti1231
Is the issue on Web or console access ? If it happens on web, shall you try to access the device by private browser mode if it still persist?
Regards,
Harry
Yes, is about web access and is still present on private too. I didn't try in console yet
Hi @Forti1231 ,
I upgraded my FGT to 7.4.5, tried to login with "qwerfdsa" and password of my admin accounts, I couldn't replicate this issue.
BTW, I have local admin accounts only, no remote admin accounts.
When you have just local admin, there is no problem.
Try to configure Tacacs+ with ascii authentication and after that, the problem appears.
Hi @Forti1231 ,
I have found an existing Mantis 1070560 matching your issue. This bug is for a combination of TACACS+ authentication + ASCII type.
The fix will be included in FortiOS 7.4.7 GA and 7.6.1 GA.
If possible, you may change to use the other authen-type settings.
Hi Forti1231,
Much appreciate if you would do packets capture on the interface that communicates with the Tacacs+ server to see how the communication is? I wonder if the mis-behavior is on the Fortigate or the server-end.
Regards,
Harry.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1662 | |
1077 | |
752 | |
446 | |
220 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.