KRB5 logmech without USER and PASSWORD parameters defaults to TD2 logmech

[healhyry]

Describe the bug

When using KRB5 logmech, user has to define USER and PASSWORD in the .profiles.yml. Otherwise, dbt will default to TD2 logmech.

Steps To Reproduce

.profiles.yml

test_dev:
  target: dev
  outputs:
    dev:
      type: teradata
      host: server.host.intra
      schema: default_db
      logmech: KRB5
      tmode: ANSI

dbt debug

12:51:36  Running with dbt=1.10.13
12:51:36  dbt version: 1.10.13
12:51:36  python version: 3.12.10
12:51:36  python path: ***\.venv\Scripts\python.exe
12:51:36  os info: Windows-11-10.0.26200-SP0
12:51:36  Using profiles dir at ***\.dbt
12:51:36  Using profiles.yml file at ***\.dbt\profiles.yml
12:51:36  Using dbt_project.yml file at ***\dbt_project.yml
12:51:36  Configuration:
12:51:36    profiles.yml file [ERROR invalid]
12:51:36    dbt_project.yml file [OK found and valid]
12:51:36  Required dependencies:
12:51:36   - git [OK found]

12:51:36  Connection test skipped since no profile was found
12:51:36  1 check failed:
12:51:36  Profile loading failed for the following reason:
Runtime Error
  Credentials in profile "test_dev", target "dev" invalid: Runtime Error
    Couldn’t  connect to Teradata Vantage SQL Engine. The ‘user’ parameter in the profile must be specified when the logon mechanism (logmech) is ‘TD2'. Correct the profile and retry.

Expected behavior

.profiles.yml

test_dev:
  target: dev
  outputs:
    dev:
      type: teradata
      host: server.host.intra
      user: ""
      password: ""
      schema: default_db
      logmech: KRB5
      tmode: ANSI

12:51:21  Running with dbt=1.10.13
12:51:21  dbt version: 1.10.13
12:51:21  python version: 3.12.10
12:51:21  python path: ***\.venv\Scripts\python.exe
12:51:21  os info: Windows-11-10.0.26200-SP0
12:51:21  Using profiles dir at ***\.dbt
12:51:21  Using profiles.yml file at ***\.dbt\profiles.yml
12:51:21  Using dbt_project.yml file at  ***\dbt_project.yml
12:51:21  adapter type: teradata
12:51:21  adapter version: 1.10.1
12:51:22  Configuration:
12:51:22    profiles.yml file [OK found and valid]
12:51:22    dbt_project.yml file [OK found and valid]
12:51:22  Required dependencies:
12:51:22   - git [OK found]

12:51:22  Connection:
12:51:22    server: ***
12:51:22    port: None
12:51:22    database: None
12:51:22    schema: ***
12:51:22    user:
12:51:22    tmode: ANSI
12:51:22    logmech: KRB5
12:51:22    account: None
12:51:22    column_name: None
12:51:22    cop: None
12:51:22    coplast: None
12:51:22    encryptdata: None
12:51:22    fake_result_sets: None
12:51:22    field_quote: None
12:51:22    field_sep: None
12:51:22    lob_support: None
12:51:22    log: None
12:51:22    logdata: None
12:51:22    max_message_body: None
12:51:22    partition: None
12:51:22    sip_support: None
12:51:22    teradata_values: None
12:51:22    sslmode: None
12:51:22    sslca: None
12:51:22    sslcapath: None
12:51:22    sslcrc: None
12:51:22    sslcipher: None
12:51:22    sslprotocol: None
12:51:22    browser: None
12:51:22    browser_tab_timeout: None
12:51:22    browser_timeout: None
12:51:22    sp_spl: None
12:51:22    sessions: None
12:51:22    runstartup: None
12:51:22    logon_timeout: None
12:51:22    https_port: None
12:51:22    connect_timeout: None
12:51:22    request_timeout: None
12:51:22    query_band: org=teradata-internal-telem;appname=dbt;
12:51:22    http_proxy: None
12:51:22    http_proxy_user: None
12:51:22    http_proxy_password: None
12:51:22    https_proxy: None
12:51:22    https_proxy_user: None
12:51:22    https_proxy_password: None
12:51:22    sslcrl: None
12:51:22    sslocsp: None
12:51:22    proxy_bypass_hosts: None
12:51:22    oidc_sslmode: None
12:51:22  Registered adapter: teradata=1.10.1
12:51:23    Connection test: [OK connection ok]

12:51:23  All checks passed!

Additional context

KRB5 auth will work if one specifies USER and PW in the .profiles.yml as empty fields.