[Mondrian] XMLA Security roles

Julian Hyde julianhyde at speakeasy.net
Wed Feb 28 05:17:31 EST 2007



From: Pedro Casals

I cannot make security roles work properly when making a query through
XMLA (it works OK if the query is done through mondrianQuery tag).
In mondrian.xmla.impl.DefaultXmlaServlet.handleSoapBody I can see this
            // use context variable `role' as this request's XML/A role
            XmlaRequest xmlaReq = new DefaultXmlaRequest(xmlaReqElem,

However, I do not see where this context is filled besides in
handleSoapHeader. handleSoapHeader function only puts this keys:

I think you're right. Whoever wrote DefaultXmlaServlet put in a hook to
use the sugested role if it is present... but it is up to the XMLA
client to set it as an attribute in the HTTP header.

One question more: If security is not implemented I would do it. I have
read XMLA 1.1 spec and I could not see where to define the role in the
SOAP message. Should it be defined as a restriction? 

The XMLA request should specify the user (probably has part of the HTTP
header, NOT par of the XML). I know Pentaho Spreadsheet Services does
this, for example.
The XmlaHandler should then resolve the user to a role (to be precise,
the user and the schema resolve to a role -- a user might run under
different roles in different schemas). We have discussed extending
XmlaHandler to use a plugin user-to-role resolver running off JNDI or
JAAS or extra information we might add extra fields to datasources.xml
to define authentication and access-control lists.
(I can't find that discussion right now... anyone??)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20070228/b05cb813/attachment.html 

More information about the Mondrian mailing list