We have our FortiAuthenticator behind a Fortigate and are being told
that we need to open up the FortiAuth to the rest of the world for port
443 to allow the token transfer facility on FTM? Does this sound right?
Is anyone running on 5.3.1? My Fortigate's are remaining on 5.6.2 based
on the chatter around SSL VPN instabilities and I would be interested to
know if anyone is using FortiAuth 5.3.1 with a pre 5.6.4 release OS
(although this is not recommended bas...
One question I have on this is that this requires the FortiAuthenticator
to be exposed to the Internet whether that be natively via it's public
address and port 443 or via a NAT translated/port map option. Either way
traffic will hit the FortiAuthent...
We have hit an issue with matching on multiple RADIUS fortinet-groups
returned from a FortiAuthenticator instance for SSL VPN users. Basically
6.0.5 appears to be only accepting one group and ignoring the rest. FTNT
has reproduced on their side and t...
Is anyone else slightly concerned about the number of bug fixes in this
release - despite it being the fifth point release on 6.0.x. This erodes
confidence somewhat when you have nearly thirty fixes in the SSL VPN
module alone. I actually had a FTNT ...
I would be interested to know now that the dust has settled on this
release how people feel about it. Currently my suite of Fortigate
clusters are sitting on 5.6.8 and I am considering a move to 6.0.4. but
wonder whether it is worth moving onto the 6...
