GitHub user ishirvani added a comment to the discussion: Add Support for SQL 
Server Analysis Services (SSAS) Connection with MDX Query Execution, Dimension 
Management, Pivot Tables, and Domain User Login

Hello,

I am working on adding support for SQL Server Analysis Services (SSAS) to 
Apache Superset, with the goal of connecting via domain user authentication and 
ensuring that once connected, the user can view the full set of data, including 
databases and dimensions.

Here’s what I’ve done so far:

Creating a new DB engine spec: I’ve implemented an initial version of a custom 
engine spec for SSAS that includes MDX query execution and fetching metadata 
like dimensions and databases. Here’s the implementation I’ve started with:

python
Copy code
from superset.db_engine_specs.base import BaseEngineSpec

class SSASEngineSpec(BaseEngineSpec):
    engine = 'ssas'
    engine_name = 'SQL Server Analysis Services'

    @classmethod
    def execute(cls, cursor, query, **kwargs):
        cursor.execute(query)
        return cursor.fetchall()

    @classmethod
    def get_dimensions(cls, cursor):
        cursor.execute("SELECT * FROM $system.DISCOVER_DIMENSIONS")
        return cursor.fetchall()

    @classmethod
    def get_databases(cls, cursor):
        cursor.execute("SELECT * FROM $system.DISCOVER_CATALOGS")
        return cursor.fetchall()
Integrating domain user authentication: My goal is to connect to SSAS using 
domain user credentials (via Kerberos or LDAP). I want to ensure that once the 
domain user is authenticated, they can view the entire dataset (databases and 
dimensions) available in SSAS.

Testing and displaying data: After the successful connection, the user should 
be able to explore the SSAS databases and dimensions through Superset's 
interface, including using MDX queries.

I would like some guidance on:

How to correctly configure the SSAS connection in Superset for domain user 
authentication, ensuring that it works with Kerberos or LDAP.
Best practices or additional steps to fully register and make this SSAS 
connection selectable and usable for users.
How to ensure that, upon successful authentication, the entire SSAS data 
(including all databases and dimensions) is properly displayed to the user 
within Superset.
Any insights or existing implementations around SSAS in Superset, specifically 
for domain user logins, would be greatly appreciated!

Thank you for your support.

GitHub link: 
https://github.com/apache/superset/discussions/33093#discussioncomment-12797469

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to