Ingesting Superset BI Data with Microsoft Azure AD Authentication

[user-2]

Original Slack Thread

how to ingestion superset BI , that require authen with microsoft azure AD <@U07FV3UHE4D>

[datahub_team]

Hey there!

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

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

[user-1]

To ingest Superset BI data that requires authentication with Microsoft Azure AD, you will need to configure the ingestion process to handle Azure AD authentication. Here are the general steps you can follow:

1. Azure AD Application Setup:

   • Register an application in the Azure AD portal. This application will be used to authenticate requests to Superset.
   • Ensure that the application has the necessary permissions to access the Superset API.

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. DataHub Ingestion Configuration:

   • Use the DataHub ingestion framework to configure the Superset source. You will need to provide the necessary credentials and endpoints for Azure AD authentication.
   • The provider parameter in the Superset ingestion configuration should be set to ldap if you are using LDAP for authentication, or db for database authentication. However, for Azure AD, you might need to customize this part to handle token-based authentication.

4. Ingestion Recipe:

   • Create an ingestion recipe that includes the Superset source configuration. Here is a basic example:

     source:
       type: superset
       config:
         connect_uri: 'https://your-superset-instance/'
         username: 'your-username'
         password: 'your-password'
         provider: 'db'  # Adjust this based on your authentication method
     sink:
       type: datahub-rest
       config:
         server: 'http://localhost:8080'
     

5. Run the Ingestion:

   • Use the DataHub CLI to run the ingestion process with the configured recipe.

If you encounter issues with authentication, ensure that the Azure AD application is correctly configured and that the necessary permissions are granted. Additionally, you may need to handle token acquisition and renewal if using OAuth2.

Would you like more detailed steps or additional information on any specific part of the process?

Sources:

• https://datahubspace.slack.com/archives/CUMUWQU66/p1724144902.308959|https://datahubspace.slack.com/archives/CUMUWQU66/p1724144902.308959
• https://github.com/datahub-project/datahub/blob/master/docs/authentication/guides/sso/initialize-oidc.md|https://github.com/datahub-project/datahub/blob/master/docs/authentication/guides/sso/initialize-oidc.md 0 button 0 button Hint: Mention @runllm in the thread for followups.

[user-1]

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.

[datahub_team]

Hi ! 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

Hope this helps ! ><