Windows Authentication not working after upgrade to 7.6 | Ideagen
Skip to main content
There's more discussions to explore simply by registering for Ideagen Community. Join us and start speaking with your peers today!

Hello,

We have a test server where we installed Q-Pulse 7.1.7 and upgraded it to IQM 7.6 and noticed that Windows Authentication no longer works.  We are still using the same Dbconnections.xml file that we had with the 7.1.7 install.  We are on a Citrix environment, but even when we run Q-Pulse directly from the application server, Windows authentication doesn’t work.

Can anyone offer suggestions on how to troubleshoot this?  Did I miss an installation step somewhere?

Hi ​@DouglasGG, are you using Windows prompted or windows automatic authentication?

If you have admin rights, edit a user account in the admin module and remove the Common Name from the account, then have the user sign in.  Does this fix the issue for that one user?


Alan,

Thank you for your reply.  We are using windows automatic authentication.  Our test database was created using a backup of our live database.  Every user has an Active Directory name associated with their account.  At the moment, I am tackling a larger problem where Q-Pulse can’t see the databases at all.  I think we have something blocking access to our database server.


Alan,

We have our database connection issue resolved.  I am not seeing where the common name entries are located within the Administration panel.  If it helps, when I try to change the authentication type, I get a “Identity Client is Invalid or Empty.  Please consider reconfigure or contact your admin” message and I am unable to change the authentication type.


Hi ​@DouglasGG, I think this is something you would need to raise a support ticket on and have one of our agents help with.  You can contact support via Ideagen Support and a member of the team can review your configuration in detail and help resolve.


Sorry for not replying sooner.  I have tried support tickets recently, but was always told to come here.  I will try again.


Sorry for not replying to this ticket.  I worked with one of your help desk representatives through a phone call and figured out the issue.  In the QPulseService.exe..config file, we needed to put in the name of our AD server in the ActiveDirectoryPath tag in <appsettings>.  Fortunately, it was an easy fix.  


@DouglasGG, glad it was sorted for you and glad it was an easy fix!


Hi ​@DouglasGG it looks like you’re still running a locally hosted Q-Pulse, have you managed to circumvent the push to the SaaS cloud version?


Reply