Hi,
wanted to check following... We use the fsso client on our enduser stations to register towards a Forti Authenticator 6.4.4. This worked fine with local ad joined devices. Since we started joining devices in Azure AD we see issues with delayed registrations. With delayed i mean 30 mins or even several hours.
Client version: 6.4.8.1755. Also tried 7.0.8.0427 btw.
In the client fclog.dat, we see something like :
program=FSSOMA msg=Failed to get computer domain name, dwSize = 0
Might be related to the issue. Does this ring a bel with anyone?
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.
Hello
There are some enhancements for Azure AD in FortiAuthenticator 6.5.x.
So I'm not sure about if it will help but I'd suggest to upgrade FAC to 6.5.4.
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.