Hi,
We need to decommission an Active Directory domain controller and are having difficulty removing it from our SSO configuration. In the Users and Device>>Authentication>>LDAP Servers page, the option to delete the LDAP server is greyed out. There's no option under the Single Sign-on page to disassociate an LDAP server from the Local SSO agent. I can't seem to find anything online on using the CLI to remove a server either (lots of info on adding them). Any help would be appreciated.
We're running FortiOS 5.2.4, and are using the Local SSO agent in polling mode.
Solved! Go to Solution.
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 probably dependences GUI is not aware of. Go CLI and check content of relevant configs.
Like:
show user adgrp <-- in there see used server and polling-id which might refer to local poller record
show user fsso-polling
show user group
In short, LDAP is used in poller, poller creates adgrp, adgrp is used in groups, groups are used in policies. So follow the dependency path from LDAP down and check the chain.
Best regards, Tomas
Tomas Stribrny - NASDAQ:FTNT - Fortinet Inc. - TAC Staff Engineer
AAA, MFA, VoIP and other Fortinet stuff
To narrow your searches run:
diagnose sys checkused user.ldap.
may be used by table user.fsso.ldap-server
may be used by table user.fsso-polling.ldap-server
may be used by table user.local.ldap-server
may be used by table user.peer.ldap-server
may be used by table user.group.member.name
may be used by table user.group.match.server-name
So all entries from User - LDAP might be used only in the above tables.
Hello,
there are probably dependences GUI is not aware of. Go CLI and check content of relevant configs.
Like:
show user adgrp <-- in there see used server and polling-id which might refer to local poller record
show user fsso-polling
show user group
In short, LDAP is used in poller, poller creates adgrp, adgrp is used in groups, groups are used in policies. So follow the dependency path from LDAP down and check the chain.
Best regards, Tomas
Tomas Stribrny - NASDAQ:FTNT - Fortinet Inc. - TAC Staff Engineer
AAA, MFA, VoIP and other Fortinet stuff
To narrow your searches run:
diagnose sys checkused user.ldap.
may be used by table user.fsso.ldap-server
may be used by table user.fsso-polling.ldap-server
may be used by table user.local.ldap-server
may be used by table user.peer.ldap-server
may be used by table user.group.member.name
may be used by table user.group.match.server-name
So all entries from User - LDAP might be used only in the above tables.
It was a dependency. However, the fix was basically to remove the entire dependency tree and start over. A little time consuming, but we got there. We also learned something new. In the latest version of code, an ADGRP can only be defined on one LDAP server. Somehow, the decommissioned DC and another DC both had the same ADGRP's defined. I think that was the conflict that forced deleting everything and starting over. Not sure how we got there to begin with, but I think we're all set now...
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 |
---|---|
1721 | |
1098 | |
752 | |
447 | |
234 |
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.