Closed cindraw closed 9 months ago
Looks like we partially implemented environment credential - for client_id/secret. The first variant shown here https://learn.microsoft.com/en-us/dotnet/api/azure.identity.environmentcredential?view=azure-dotnet
I'll see if I can add at least the username/password and maybe the certificate-based one.
A workaround would be to create an env var AZURE_CLIENT_SECRET and just set it to a dummy value. But I will try to implement the checks correctly
Describe the bug Initializing environmental variables for username and password as follows gives an error when trying to connect to a Log Analytics Query Provider when
auth_methods
is set only forenv
.To Reproduce Steps to reproduce the behavior:
QueryProvider
-from msticpy.data.data_providers import QueryProvider
msticpyconfig.yaml
with'auth_methods': ['env']
QueryProvider.connect()
Expected behavior No errors and successful connection to the pointed Log Analytics Workspace
Screenshots and/or Traceback Stack trace seem to indicate that the
env
authorization method fails because no (applicable) environmental variables exist. See context for more information.Environment (please complete the following information):
Additional context It seems there are contradiction between the documentation and the actual working code:
Please let me know if the feature was removed or if it's planned for addition any time soon.