Is LDAPS supported?

[anpa8]

Hi,

is LDAPS supported with this provider?

Regards,
Angelo

[jvdgaag]

Hello there,

That is something I'd like to know too.
I'm already getting questions from a customer about this.
Microsoft is going to enforce LDAPS because of a potential security issue with LDAP.

Sincerely,
Jan van der Gaag

[sawest]

The module is built on top of System.DirectoryServices. All domain connections are handled through System.DirectoryServices. I have not personally tested LDAPS but I have no reason to believe that the module would not work with LDAPS. If someone would like to test it, that would be much appreciated.

[sawest]

This module will NOT currently work with LDAPS in its current state. It has the ability with some mild code refactoring. Hopefully I, or someone, can get to this soon.

[sawest]

duplicate #73

[StefanoPagana]

We will soon migrate the domain from LDAP to LDAPS.
With a little help I could try to implement this functionality.

Do you think it would work to replace the hard-coded LDAP:// strings in the solution?

[MaiklT]

I think the best ways would be

• either a setting to choode LDAP or LDAPS (Example: Checkbox "Secure")
• or a fallback - try LDAPS, if this does not work, try LDAP

[sawest]

I have had success in making this work by using LDAP://:636 in the root domain and changing authentication type to secure. Would love it someone could try this and provide feedback with your experience.

[anpa8]

I have had success in making this work by using LDAP://:636 in the root domain and changing authentication type to secure. Would love it someone could try this and provide feedback with your experience.

Hi,
i did try this, but after update there is no settings page in the tab "website settings". With Old version i have here the settings for connection to AD. It shows only an error message:

DNN Error
Es gibt zur Zeit keine Website in dieser Installation. - 503 Dienst nicht verfügbar (there is actual no website in this installation. 503 service not available)

Addtional Error Message:

Message:C:\inetpub\wwwroot\dotnetnuke-dev\DesktopModules\AuthenticationServices\ActiveDirectory\Settings.ascx(12): error BC30456: "Page" ist kein Member von "ASP.desktopmodules_authenticationservices_activedirectory_settings_ascx".

StackTrace:

InnerMessage:C:\inetpub\wwwroot\dotnetnuke-dev\DesktopModules\AuthenticationServices\ActiveDirectory\Settings.ascx(12): error BC30456: "Page" ist kein Member von "ASP.desktopmodules_authenticationservices_activedirectory_settings_ascx".

InnerStackTrace:

   bei System.Web.Compilation.BuildManager.PostProcessFoundBuildResult(BuildResult result, Boolean keyFromVPP, VirtualPath virtualPath)
   bei System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode, Boolean ensureIsUpToDate)
   bei System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath, Boolean ensureIsUpToDate)
   bei System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
   bei System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
   bei System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath)
   bei DotNetNuke.Modules.Admin.EditExtension.AuthenticationEditor.get_SettingsControl()
   bei DotNetNuke.Modules.Admin.EditExtension.AuthenticationEditor.Initialize()
   bei DotNetNuke.Modules.Admin.EditExtension.EditExtension.BindData()
   bei DotNetNuke.Modules.Admin.EditExtension.EditExtension.OnLoad(EventArgs e)
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Control.LoadRecursive()
   bei System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

[sawest]

Version 8 targets .Net Framework 4.8. Can you verify that .Net Framework 4.8 is loaded on the server that is experiencing this error?

And/or could you retarget the project to version 4.7.2 and recompile and see if you still get the same error? I am not sure we have to target the 4.8 framework if its causing issues.

[anpa8]

Hi, i have compiled it with target framework 4.7.2, but still won't work.
On the Server 4.8 is installed, but, when i look at dnn server information, i got this:
Version des .NET-Frameworks:
4.0.30319.42000

So i believe this is wrong?

[sawest]

I believe the server info shows the version of the app pool itself. That should be fine.

Once you built it, did you actually install the new extension install package or did you must copy over the DLL it built? I am wondering if the new DLL is there but settings.ascx didn't update and the old version of settings.ascx is being used. Installing the new package will copy over all those files to right location.

[anpa8]

Yes, i'll do an Install with new ZIP File.

Could try to deleted Extension and do a fresh Install, without Update.