It's smooth!

Desktop is authenticating on launch, now if I can only get the web module to login... not quite there today...

And done!

Web module authenticating!

A great Chrissie bonus!

I have managed to get the AD module in HMPV8 working in terms of talking to the AD DB via LDAP.

However I am struggling with getting the web module to authenticate within the browser.

I have everything configured correctly.

Two funny things I have noticed:

1) In order to be able to choose to make the virtual directory hmplogin run as ASP.net 2.0, I had to make it run as an IIS application by clicking "Create" under Application settings under the virtual directory tab for hmplogin. 

2)Web Admin keeps changing the “Authentication Virtual directory” path back to HMPWEB instead from hmplogon, it won't seem to hold the configuration.

Any tips anyone?

We've finally managed to get the Windows authenticated login (ie. AD login) for Web Module working for Nathan Hood.  It turns out that the AD login was turned off in AD Manager.

If you are using v8, you must make sure that automatic HelpMaster Pro Active Directory logon is enabled by following the steps below:
1. Log into the HelpMaster Pro Active Directory module
2. Click on the HelpMaster Pro tab
3. Check the checkbox entitled "Allow automatic HelpMaster Pro login with Active Directory credentials"

In v8, this setting is a "universal setting" - meaning "enabling/disabling this will do so for the entire suite of HelpMaster applications" (quoted from the v8 help file) and this includes the Web Module.  In v9, this has been simplified and you are not required to follow the above steps as long as you enable the AD login using the Web Admin utility.  Ofcourse, you are still required to run the HelpMaster Pro Active Directory Manager and configure the AD module (eg. map the HMP clients and the AD users etc.) and follow the Web Module configuration steps as instructed in the help file.

In v9, we've also improved the user feedback process in case it fails to access a secure page due to AD login failure.  For example, if the user is already logged into the database, the AD login in v8 just fails and the user is taken to the sign in page without any feedback. In v9, users will be provided the option to continue on and close the previous login sessions - much like the way it's handled for normal logins.