{{#if (not signed_in)}} {{#is help_center.name "Ideagen Help"}} {{#link "sign_in" class="unified-navigation--btn-primary"}}Sign in{{/link}} {{else}} {{#link "sign_in" class="unified-navigation--btn-primary"}}Sign in{{/link}}
{{/is}} {{/if}} {{#if signed_in}}
{{#is help_center.name "Ideagen Help"}}
Manage tickets
{{else}} {{#link "requests" role="menuitem"}}
Manage tickets {{/link}} {{/is}}
Update profile
Change password
Privacy Policy
Terms of Use
{{#link "sign_out" role="menuitem" class="signOut"}}
Sign out {{/link}}
{{/if}}
{{user.name}}
Looking for help?
Common queries
Send us feedback
Before you start
This form is for Ideagen Luminate feedback only.
Your submission will not receive a response. To request solution support, open a ticket with us.
We'd love to hear your thoughts on features, usability, or what you love about Ideagen Luminate.
Solved
Windows Authentication not working after upgrade to 7.6
+2Hello,
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?
Best answer by DouglasGG
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.
+8Hi
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?
+2Alan,
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.
+2Alan,
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.
+8Hi
+2Sorry for not replying sooner. I have tried support tickets recently, but was always told to come here. I will try again.
+2Sorry 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.
+8
Hi
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.