| Description |
This article describes a scenario where the FSSO may not work properly after a sudden time and without changing anything in the configuration.
It is possible to check that by navigating to Windows Server -> 'Fortinet Single Sign On Agent Configuration' -> Collector Agent Status: NOT RUNNING but no changes were made at the FortiGate unit and at the Fortinet Single Sign On Agent Configuration.
 |
| Scope |
FortiGate v7.x. |
| Solution |
Go to Windows Server -> Search: Services -> Select 'Services'.
Scroll down and go to 'Fortinet Single Sign On Agent Service': select it.
Go to the 'Log On' tab -> Put the current password following the account -> 'Password' and “Confirm password” -> OK.
It will show a Services pop-up message with 'Windows could not start the Fortinet Single Sign On Agent Service service on Local Computer. Error 1069: The service did not start due to a logon failure.' -> Select OK -> Select OK.
Go to 'Fortinet Single Sign On Agent Service': 'Right Click' -> Select 'Stop'.
Go to 'Fortinet Single Sign On Agent Service': 'Right Click' -> Select 'Start'.
Go to Windows Server and go to 'Fortinet Single Sign On Agent Configuration' -> Collector Agent Status: RUNNING. It will show Collector Agent Status: RUNNING after that.
Although no setting was changed at the FortiGate unit and also at the 'Fortinet Single Sign On Agent Configuration' the account at Windows Server expired and the new password had been changed. Then it can be relevant to go to 'Fortinet Single Sign On Agent Service' to enter the current password again. It can be necessary to stop and start the service again too. |
