Please summarize your question in one sentence
Migrating from a working module and receiving the error "Could not access LDAP to obtain domains info" on a solid green background, and the login doesn't work.
Give a more extended description
We have a website that was originally on an earlier version of DNN 9 that we have updated to 10.2.5 running on Windows Server 2019 with IIS v10. It is currently using a different Active Directory module, but the auto sign-in feature never worked on that one, so we want to migrate over to this module instead.
When I try to configure this, though, I'm getting a couple of different errors. Whether I'm using what the tooltips recommend or the working settings from the other module doesn't seem to make any difference.
First, I get a red error when accessing the provider's site settings with an "object not set to instance of object" error. That seems to go away, though, if I checked "Windows authentication?" and save. Just wanted to point that out since that is how it is right out of the box.
The main issue is that no matter what I try, I get the following on a solid green background:
Accessing Global Catalog:
OK
Checking Root Domain:
OK: LDAP://dc2.clientdomain.local
Accessing LDAP:
OK
Find all domains in network:
Could not access LDAP to obtain domains info
and login attempts fail without anything being added to the admin logs.
I also don't see a way to set this as the "default authentication provider" in Settings > Security, and I am not seeing a module to replace the default login module with.
Steps to reproduce (if needed)
Other comments or remarks
The active directory has over 1400 different groups, and that caused the other module to have issues, so we are wondering if that is an issue here.
Please summarize your question in one sentence
Migrating from a working module and receiving the error "Could not access LDAP to obtain domains info" on a solid green background, and the login doesn't work.
Give a more extended description
We have a website that was originally on an earlier version of DNN 9 that we have updated to 10.2.5 running on Windows Server 2019 with IIS v10. It is currently using a different Active Directory module, but the auto sign-in feature never worked on that one, so we want to migrate over to this module instead.
When I try to configure this, though, I'm getting a couple of different errors. Whether I'm using what the tooltips recommend or the working settings from the other module doesn't seem to make any difference.
First, I get a red error when accessing the provider's site settings with an "object not set to instance of object" error. That seems to go away, though, if I checked "Windows authentication?" and save. Just wanted to point that out since that is how it is right out of the box.
The main issue is that no matter what I try, I get the following on a solid green background:
and login attempts fail without anything being added to the admin logs.
I also don't see a way to set this as the "default authentication provider" in Settings > Security, and I am not seeing a module to replace the default login module with.
Steps to reproduce (if needed)
Other comments or remarks
The active directory has over 1400 different groups, and that caused the other module to have issues, so we are wondering if that is an issue here.