User Cannot Be Authenticated in NPrinting despite being valid domain user

[rnoh]

I have a specific user that is unable to login to NPrinting and use any of its functions on Qlik Sense apps. She is a verified NT Domain user that has all the correct privileges but is being asked to authenticate and not being recognized when trying to use a On Demand object or log into Newsstand.

[David_Friend]

@rnoh have a look at this article from Sebastien:

https://community.qlik.com/t5/Official-Support-Articles/NPrinting-Designer-errors-out-with-The-curre...

Verify if the cookie.prefix value was changed

1. Check the app.conf in C:\ProgramData\NPrinting\webconsoleproxy for the lines:
   

   #The session cookie prefix.
   cookie.prefix=NPWEBCONSOLE​

2. if the cookie.prefix is changed from the default value above, uncomment or change it back to the default.

Is this just 1 user that is affected? What if they try from different browsers, or maybe use incognito mode?

[Lech_Miszkiewicz]

Hi @rnoh 

1. What does this user see when they access NPrinting directly and try to login to admin console using blue "Windows Login" button ? 

Confirming that this user is able to login directly will hel troubleshoot issues. 

If there is a problem with SSO using this blue button you can then start troubleshooting by using web browser browser developer tools.

2. Does this user have nprinting Role assigned allowing to use OnDemand? - double checking this despite your comment regarding right privlidges.

cheers

Lech

[rnoh]

Clicking the blue Windows Login button opens a login prompt from NPrinting. The user has the proper security role assigned to their user.

[David_Friend · Accepted solution]

@rnoh what is your authentication, SSO?

[rnoh]

We are using SSO, the issue was resolved by deleting an old user in NPrinting under the user's old name and domain account. It seems that this created some kind of conflict with the SSO service. 

[David_Friend]

gosh that sounds familiar, did they have a name change recently?

[Lech_Miszkiewicz]

That looks more like the actual domain account was different - the name itself does not really matter, all what matters is domain account attribute and if that was wrong then it couldnt work, but if that was the correct then I am really surprised.