We previously briefly covered the updates to XLCubedWeb to support single sign-on using SAML 2.0, in this blog we will go through the process needed to setup SSO in XLCubedWeb using Okta and the steps required to map the users through to cube-defined roles in Analysis Services.
With the upcoming maintenance release of V9.2 we are introducing support for Single sign-on in XLCubedWeb, this can be configured to use any SAML 2.0 identity provider and provides some useful functionality for integrated user-level data access in Analysis Services.
For the moment Analysis Services only supports windows-based authentication, and many of our customers are using single-sign on providers to authenticate users and provide application access. As part of our single-sign on solution we give the ability to define the Analysis Services access level for the users in the identity provider (or via a custom SQL lookup if access level mapping is stored outside of the provider).
This allows customers to setup SSO and still allow different users to have different access to different cube levels. To do this XLCubed makes use of the “EffectiveUser” and “Roles” connection properties, these properties allow the connection to run as a particular user or in the context of a cube-define role.
The following gives an overview of the process when using role mappings stored in the identity provider:
Or if using SQL to provide the user to role mapping:
You can see more about the setup process on the following page:
We will also look at a practical example of setting up single sign with role mapping in a future blog
A common scenario in business reporting is for different users to want reports to open with ‘their’ view on the data. So for a particular Store or business unit.
Many back-ends already support setting Default Members for different users and groups, for example Analysis Services allows this, but as XLCubed can connect to an increasing number of back-ends we can’t rely on this and sometimes a single report user may have different combinations of views on data (for example, a set of store/product group combinations)
Version 9.2 of XLCubed has added Workbook Aspects to help with this, allowing users to store their own slicer selections and quickly switch between those and also to set the default for when the report is loaded.
With this feature you can define the aspects at a report level, shared by all users, and also allow users to define their own private aspects.