We notice that in the current XMLA driver implementation, the HTTP authentication is hardcoded to HTTP Basic.
If the server uses another authentication scheme like HTTP Digest (much more secure as the password itself is not transmitted) Olap4J fails to connect.
There are several ways to support HTTP authentication more widely:
A clean way would be to rely on a full featured HTTP library like Apache HTTPClient. But that would add more jar dependencies to Olap4J.
Another way is to stick with what the JDK provides: the java.net.Authenticator design described in this article: http://download-llnw.oracle.com/javase/6/docs/technotes/guides/net/http-auth.html
Log in to post a comment.