After installing QV11SR2 and https certificate, alternate login page (web form) only allows server admins. Anyone get this?

[#1]

As the question says, after installing QV11SR2 and https certificate, alternate login page (web form) only allows server admins. Default login page (browser authentication) works as normal. Anyone get this? The only other manual change made after the upgrade was to tick on https on port 443.

Thanks

[agigliotti]

Hi.

I want to have single sign on between sharepoint (or any given .NET app) and Qlikview.

What I did:

I created a "validate.aspx" file and added the following code on the codebehind:

Response.Headers.Add("QVUSER","obracho");

Response.Redirect("http://qviewserver/QlikVIew/index.htm");

As it didn't work, I also tried this:

NameValueCollection headers = HttpContext.Current.Request.Headers;

headers.Add("QVUSER","myusername");

Response.Redirect("http://qviewserver/QlikView/index.htm");

And that didn't work neither.

I always get a "Login Failed" message.

• Do you have any clue (or any documentation available) regarding how to do this?
• Is there any other / alternative way of doing it?
• How are the people that are doing SSO integration with qlikview doing it?

Thanks for your help !

[Rajesh4]

When you use Alternate login page (web form) , we need to login as DOMAIN\UserID. Previously i.e. before SR2, it used to work even if we do not append the DOMAIN. Also try disabling windows authentication on all virtual directories, if you are using IIS.

[Rajesh4]

When you use Alternate login page (web form) , we need to login as DOMAIN\UserID. Previously i.e. before SR2, it used to work even if we do not append the DOMAIN. Also try disabling windows authentication on all virtual directories, if you are using IIS.

[Rajesh4]

When you use Alternate login page (web form) , we need to login as DOMAIN\UserID. Previously i.e. before SR2, it used to work even if we do not append the DOMAIN. Also try disabling windows authentication on all virtual directories, if you are using IIS.

[#6]

We are not using IIS, and we have tried DOMAIN\user on a variety of browsers, unfortuantely its still as it was - i.e. if you are an administrator on the machine it works, if you aren't it doesn't.

We are still investigating though as it seems we had fixed it on a seperate cloned VM setup, but we where caught up with other more urgent work and decided to leave it with just using popup authentication (default) for now. 

If we manage to solve this, I will post here, in the meantime thanks for the advice.

[Miguel_Angel_Baeyens]

Hi,

By default, admins in the AD are created without limitation on which computers they can log on. Go to the Domain Controller, search for the user not able to log in, then right click on the user properties and make sure in the Log On tab that he has access to "All Computers".

Hope that helps,

Miguel

[ali_hijazi]

same thing happened to me what is the resolution?

[#9]

Hi,

    Have you checked the Service Account that you used to start the QV Services ?

    You're using a Local Account or Domain Account to start the QV Services ?

Regards,

Kho

[mls]

When Using Alternate Login Page, the AccessPoint will redirect to the FormLogin.html page for authentication.
This page will pass the user/password to the Authenticate.aspx which will in turn validate the credentials on the server machine.

For this to work, the user needs to have the right to "Log On Locally" on the server.

So the users that should be able to log on have to be added into this group (Procedure described here Error Message: The user has not been granted the requested logon type at this computer).

[ali_hijazi]

that's correct I had the same problem and we gave the qlikview user the permission to log in from any pc and it worked