I have Qlik Sense Server hosted behind a 3rd party Proxy.
But the user should never have access to "B" directly -- the user shouldn't be aware that "B" exists at all.
All Qlik sense requests work correctly, going from my client at origin "A" , to the domain "A", and responses come back successfully.
Then it the hub's getUserInfo function sends a request to:
Specifically the getUserInfo sends request to:
But the response comes back:
So then in the hub/core/services/comm/authentication initialization,
it sets a.logoutUri = https://B/qps/user
Why is inconsistent domain, now "B"? Shouldn't Qlik Sense server respond with logoutUri set to domain A?
After all this, when I attempt to logout, my browser sends a DELETE request to domain B, from domain A.
This is cross-origin request (CORS), so my browser sends a pre-flight request.
Any advice here? Thank you!
Message was edited by: Nathaniel Anderson removing the auto-linking behavior against non-URLs like "https://"