OPTIONS - extra_params, is it working?

[gitpickle]

It appears to me that "extra_params" is not working. I can place values in this string than don't match any valid key or invalid values in the dictionary, and no changes result at runtime.

e.g. -

'OPTIONS': {
 'extra_params': 'User=lutzm1;TrustServerCertificate=yes;Uid=lutzm1;Password=',
}'

Any thoughts?

Mike

[rjschave]

Are you able to connect to the database?

Here is what I use to connect to a SQL instance that doesn't have encryption/SSL, using the ODBC 18 driver:

'default': {
        'ENGINE': 'mssql',
        'HOST': env('DATABASE_HOST'),
        'PORT': env('DATABASE_PORT'),
        'NAME': env('DATABASE_NAME'),
        'USER': env('DATABASE_USER'),
        'PASSWORD': env('DATABASE_PASSWORD'),
        'OPTIONS': {'driver': 'ODBC Driver 18 for SQL Server', 'extra_params': "Encrypt=no"},
    },

If I don't include the Encrypt setting in extra_params, I can't connect to this database. This suggests to me that extra_params is working.

[gitpickle]

Hmm. Is the intent of extra_params to be blindly pulled into the connection string?

[gitpickle]

Ultimately what I am trying to accomplish is - authenticate with AD (integrated) authentication but supply a custom userid and password other than the identity of the executing process. I need to deploy to Linux and my organization is currently unable to attached our Linux machines to our domain. Sigh.

[rjschave]

This page lists the key/value pairs you can pass in extra_params. The authentication section may be of interest.

Can you try adding 'authentication': 'ActiveDirectoryPassword', to OPTIONS? Make sure you username is username@domain.

Edit to add, I believe you need SQL Server 2017 or above for AD authentication.