You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We previous use the below parameter to connect Kusto.
from sqlalchemy_kusto import connect
# Define your Kusto connection details
kusto_url = "https://<kusto_cluster>.kusto.windows.net"
database_name = "<your_database_name>"
kusto_client_id = "<your_client_id>"
kusto_client_secret = "<your_client_secret>"
kusto_tenant_id = "<your_tenant_id>"
# Connect to Kusto using AAD authentication
connection = connect(
cluster=kusto_url,
database=database_name,
msi=False,
azure_ad_client_id=kusto_client_id,
azure_ad_client_secret=kusto_client_secret,
azure_ad_tenant_id=kusto_tenant_id,
)
# Execute a sample query
result = connection.execute("select 1").fetchall()
print(result)
However, secret is not supported due to security concern. Is it supported to use the access_token returned from service principal as the authentication in kusto?
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We previous use the below parameter to connect Kusto.
However, secret is not supported due to security concern. Is it supported to use the access_token returned from service principal as the authentication in kusto?
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: