Created on 10-13-2016 06:58 AM Edited on 05-26-2022 07:18 AM By Anonymous
Description
This article is to describe what may need to be done in AO in order to re-instate External Authentication in 3.7.4
There may be issues with External Authentication’s Configuration based on some Module changes and requests against your DC on this version going forward
1 – If you are running into a login problem with AO through External Authentication, please attempt to login using your default admin username into the super (global)
2 – If you are unable to login, please follow the related KB article "How to reset the admin password for AO" in order to provide yourself a login temporarily.
3 – Once you’ve created this test user login, please log in with the test user and head to Admin > General Settings > External Authentication
4 -- Remove the Base DN under External Authentication
5 -- Test the user name but make sure that you are aware of case sensitivity on login user names.
On 3.7.4+ one of the biggest changes is the way we use external authentication. When you push a new Base DN into the external authentication tab, it appends those values to the user in CMDB.
In Theory, once you finish discovery LDAP, you can include the external authentication credentials to Admin > General Settings > External Authentication without applying another BASE DN, and it will allow you to authenticate. Test this out several times.
If you are having difficulty please call support.
3.7.4+
Related Articles
Technical Note: How to reset the admin password for FortiSIEM
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.