|
I'd like to run Saiku through a reverse proxy which is already using basic auth. As the communication between Saiku and Saiku Webapp triggers another basic auth exchange, the user's existing session is cleared. I could just create the same users in Tomcat as I have in the reverse proxy, but I'd rather disable Saiku security completely. Is there a simple tweak to the application context XML that allows to do this? |
|
in the more recent builds of saiku (last 2 weeks) i changed the auth completely and we dont use basic auth anymore. just download the latest version at http://ci.analytical-labs.com/ and let me know if that fixed your issue Yeah thanks I got it working with 2.2, I've just hardcoded a user that logs in automatically in Settings.js (as you do for the demo site). Now our Apache Reverse Proxy controls who can access Saiku, and internally it just uses this single user (also nice because we want the users in this case to be able to share / group-edit saved queries).
(22 Feb, 11:41)
JJ Morris
|
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Tags:
Asked: 31 Oct '11, 13:13
Seen: 581 times
Last updated: 22 Feb, 11:41
BTW I'm using the standalone webapps.