ILocation Interface
Assembly: Qlik.Sense.JsonRpc.dll
Interface for Qlik Sense instance location handling
Syntax
public interface ILocation : IGenericLocation, IDisposable
Properties
Name | Description |
---|---|
CustomUserCookies |
Property for custom user cookies |
CustomUserHeaders |
Property for custom user headers |
CustomUserUrlParameters |
Property for custom url parameters |
SessionCookie |
Gets the session value cookie of the Qlik Sense instance. |
VirtualProxyPath |
Virtual path to the proxy |
Methods
Name | Description |
---|---|
AsAnonymousUserViaProxy(Boolean) |
Defining the location as a connection to Qlik Sense as an anonymous user. |
AsDirectConnection(String, String, X509Certificate2Collection, Boolean) |
Defining the location as a direct connection to Qlik Sense using a specific user. Connection will be made to port 4747 unless port is explicitly stated in location URI. |
AsDirectConnection(String, String, X509Certificate2Collection, Int32, Boolean) |
Defining the location as a direct connection to Qlik Sense using a specific user. |
AsDirectConnectionToPersonalEdition() |
Defining the location as a direct connection to Qlik Sense Personal. Connection will be made to port 4848 unless port is explicitly stated in location URI. |
AsDirectConnectionToPersonalEdition(Int32) |
Defining the location as a direct connection to Qlik Sense Personal. |
AsExistingSessionViaProxy(String, String, Boolean) |
Defining the location as a connection to Qlik Sense using an existing session. |
AsJwtViaProxy(String, Boolean) |
Defining the location as a connection to Qlik Sense using JWT Authentication. |
AsNtlmUserViaProxy(NetworkCredential, Boolean) |
Defining the location as a connection to Qlik Sense using NTLM Authentication. |
AsStaticHeaderUserViaProxy(String, String, Boolean) |
Defining the location as a static header connection to Qlik Sense using a specific user. |
AsTicketViaProxy(String, Boolean) |
Authenticate using an ticket retrieved from a Qlik Proxy Service (QPS). |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!