We're using a third-party tool for second-level authentication. So, basically, we integrated our Office 365 to Active Directory for additional service, and our users need to provide the SSH people to log in. So we wanted to use that ticket, which is not scalable. So that's why it should be what we basically use FortiToken for now is to ensure that administrators who log into the box have to provide additional proof at the DCB app.

We use the solution for two-factor authentication. If anybody we have set up on FortiAuthenticator needs two-factor authentication to log in, we use FortiToken.

All users who can log in on Fortinet have Token. We have 15 FortiTokens for the managers who are connected to the VPN and also for those who are connected to the software. It is mobile, not a hard token. That said, I have the hardware token, which is related to the administrator, me, and my assistant. It's used on software and hardware. We use it at an administrator level and at a user level. 

I have used the solution for VPN access.

We use the solution only with Fortinet products for VPN.

We're aiming to provide every user with mobile token-based two-factor authentication (2FA) to enhance security.

It's for internal security.

The name of the authenticator is from the user's site. It's sufficient for that to provide you with a number when you need to access a protected resource, which is the site. This is two-factor authentication. You have two layers of authentication. The first layer is provided by the name and password, and the second layer is provided by the authenticator. 

So you have to be attentive to that when the app prompts you, or at least the app prompts you, which advises you about the directive that someone is attempting to access this technology. And you can confirm by saying yes. It's directly linked to the internal access attempt to the site.

We are using Fortinet FortiToken for token-based mobile applications.

We only use FortiToken for authentication purposes, like logging into SSL VPN or plugging into firewalls.

We use Fortinet FortiToken when a client requires it.

The FortiToken from Fortinet is primarily used for VPN authentication. That is one of the most common use cases. VPN authentication as well as two-factor authentication on VPN. In addition, two-factor authentication is required for administration access to the FortiGates.

In the rare case where the FortiAuthenticator is separate, they use it as a directory for the enterprise. It can also be used for other applications such as Microsoft. External applications and, on occasion, customer applications that use RADIUS.

We use Fortinet FortiToken to do a double authentication for people who work out of the company.

We use FortiToken to authenticate many of the applications we and our clients use. We use, integrate, and resell the solution.

We are using it for VPN. We have its latest version.

We are using this solution for administrator access to firewalls. We have its latest version.

I'm a solution provider who sells FortiToken and helps customers implement it. Most of my clients use Fortinet solutions like FortiClient VPN and FortiGate firewalls for remote work. They also use FortiToken for authentication. 

FortiToken is a second-factor authentication solution mapped to the on-prem firewall. Any user who connects to the firewall for VPN uses the token for authentication. Our client is the end-user, and we manage it for them. We acquired FortiToken five years ago and additional tokens every year since then. The token is just a piece of hardware, so there's nothing to be refreshed over there.