Ingesting Superset BI Data with Microsoft Azure AD Authentication Workaround

ingestion
1

Original Slack Thread

how to ingestion superset BI , that require authen with microsoft azure AD
give me some workaround

2

Hey there! :wave:

<@U06TM7M40RK> Can you help with the questions in this thread?

:information_source: Please continue to tag RunLLM (e.g <@U06TM7M40RK>) to have it continue generating responses!

3

To ingest Superset BI data that requires authentication with Microsoft Azure AD, you can follow these general steps. However, please note that the specific integration of Superset with Azure AD for authentication might require some custom setup, as direct support for Azure AD authentication in Superset ingestion is not explicitly documented in the provided data sources.

General Steps for Superset Ingestion with Azure AD Authentication

  1. Set Up Azure AD Application:

    • Register an application in the Azure AD portal with the necessary permissions to access Superset. This includes setting up client ID, client secret, and redirect URIs.

  2. Configure Superset for Azure AD Authentication:

    • Ensure that your Superset instance is configured to use Azure AD for authentication. This typically involves setting up OpenID Connect (OIDC) or OAuth2 with Azure AD as the identity provider.

  3. Ingestion Configuration:

    • Use the DataHub ingestion framework to configure the Superset source. You will need to provide the necessary authentication details (client ID, client secret) in the ingestion recipe.

  4. Custom Authentication Handling:

    • If Superset is configured with OAuth2/OIDC, you might need to handle token acquisition and refresh manually. This can involve writing a custom script or modifying the ingestion pipeline to include steps for obtaining an access token from Azure AD.

  5. Run Ingestion:

    • Execute the ingestion process using the DataHub CLI or UI, ensuring that the authentication tokens are correctly passed to access the Superset API.

Example Configuration

Here is a basic example of what the configuration might look like, assuming you have set up the necessary Azure AD application and Superset is accessible via an API:

source:
  type: superset
  config:
    connect_uri: 'http://your-superset-instance:8088'
    username: 'your-username'
    password: 'your-password'
    provider: 'db'
    # Add any additional configuration for Azure AD token handling
sink:
  type: datahub-rest
  config:
    server: 'http://localhost:8080'

Additional Considerations

  • Token Management: You may need to implement a mechanism to handle token refresh if the access token expires during the ingestion process.
  • Permissions: Ensure that the Azure AD application has the necessary permissions to access Superset resources.
  • Debugging: Enable detailed logging to troubleshoot any issues related to authentication or data access.

If you need more detailed steps or specific code examples, please let me know!

Sources:

4

Hi, how did my answer work out for you? Need any more assistance? You can also tag <@U07FV3UHE4D> to let your fellow community members know you’re still looking for guidance.

5

Hi :slight_smile: ! Did this interaction resolve your issue or do you still require assistance ?

Please tag @ RunLLM if you still need further assistance !

Or tag @Datahub Community Support if you require a person to take a look :slight_smile:

Hope this helps ! ><