FortiToken configuration example
To configure FortiToken objects for FortiToken management, follow these steps:
- In the object tree menu, browse to User& Device > FortiToken.
- Select Create New from the lower content frame toolbar.
- Type the serial number or serial numbers of the FortiToken unit or units and select OK to save the setting. Up to ten serial numbers can be entered.
- Browse to User& Device > UserDefinition to create a new user.
- When creating the new user, select Enable Two-factorAuthentication, and then select the FortiToken from the drop down menu.
New local user window
- Browse to User& Device > UserGroup, create a new user group, and add the previously created user to this group.
- Install a policy package to the FortiGate, as described in Install a policy package.
- Install a policy package to the FortiGate, as described in Install a policy package.
- On the FortiGate, select User> FortiToken. Select one of the newly created FortiTokens, then select OK to activate the FortiToken unit.
Question about ADOMs. In previous versions of FortiOS 4.3 maybe earlier. When you had multiple devices under an ADOM the policies and objects were clearly separated per device being managed. With the newer FortiOS it seems as though there is overlapping and my policies and objects seem to be cross contaminated between devices. What is your perspective on this and/or work around? Thank you in advance – Richard
I always keep my devices separated by Firmware version. ADOM 4.3 ADOM 5.2 ADOM 5.4 etc to keep things nice and neat.
I have an issue for deleting the V4.2 ADOMs from FMG V5.2 getting the below error.
Some ADOM(s) were not deleted successfully because they are not empty
But those ADOMs are not used anywhere. How to find out where it is used?
No admin accounts having access to the ADOM, No policy package for the ADOM.
Usually, it experiences this issue because something somewhere is still referencing it. Whether that item be a policy package as you mentioned before or a group etc.
Is there any possibilities to find out the references for that ADOM on the FMG.
Hi Mike,
We use fortimanager v5.4.1-build1082 160629 (GA) FMG-VM64 but we cant drag and drop within the rule base. (drag en drop from the object side plain does work) I have seen a instruction video were they lock the adom but also that future is non exsistent in our GUI.
You have any idea what this could be ? I did not see any issues on this subject on the fortinet site. We have upgraded from a older version FM.
kind regards and thanks for this great support site, i look here first!
Did you follow the supported upgrade path when you moved your FortiManager up through the code?
Not sure ( I was not involved and there is no change history) but i did found this in the “alert message console”
Upgrade image from v5.2.7-build0757-160408(GA) to v5.4.1-build1082-160629
Hello,
HELP !! we have multiple firewalls we would like to upload on our Fortimanager in the same ADOM.
The problem is that some objects have the same names but different IPs adresses. i read that the only solution is mapping the objects. if we do so we will have to it manually on every object (more than ~200) which is not an option for me. Can you please help me with this problem ?