4 Replies Latest reply: Jan 4, 2018 2:25 PM by Gregory Sarrica RSS

    Qlik Sense Login for internal extension mashup

    Gregory Sarrica

      I have created a mashup on my qlik sense server. It is hosted on the qlik sense server itself as an extension. The mashup uses an app that requires authentication. Is there a way to redirect to qlik sense's normal login screen (https://myqliksenseserver.com:4244/form/) and then back to the mashup to handle the authentication?


      All I can tell is that the normal login screen can only take a "target_id" as a parameter, that has to be an app guid. I don't believe mashups have these.


      Right now when I browse to the mashup while not logged in I get an error popup saying:


      An error occurred

      You cannot access Qlik Sense because you have no access pass.

      Then also:

      Access to the app is denied: NoAvailableAccessType


      Any ideas on how I can handle this?

      Thank you.

        • Re: Qlik Sense Login for internal extension mashup
          Satish Kurra

          Not sure if this can be done.


          I'm using the same approach as you but restricting the user access in stream and APP level.


          Example: Stream: Test, App: Test.qvf


          Once imported your extension, will allow automatic access to users who are associated to stream Test


          Hope this helps.




          • Re: Qlik Sense Login for internal extension mashup
            Francis Kabinoff

            A few tips.


            First, the target_id parameter is not an app guid, it's generated by Qlik Sense based on the redirectUri parameter on the websocket request. Any resource behind a virtual proxy can be used. So if your mashup is behind a virtual proxy (hosted on Qlik Sense server by Qlik Sense), then you're good to go. If not, then what I do is upload a simple html document to the content library which just simply redirects to my mashup. Then I set the redirectUri in the mashup config to point to that html document, which redirects to the mashup. Again, this is only necessary if your mashup is not behind a virtual proxy.


            Second, the reason you are seeing the "no access pass" is because you have not allocated any tokens for "Login access." When a mashup loads, it loads some resources that require a token, and since the user doesn't have a user token before logging in, these resources are unable to load. Allocate a few tokens to "Login access" and anonymous users, and then you won't see the "no access pass" any longer, and your mashup should redirect to the auth module defined in the virtual proxy if a user is not authenticated.