Uid

Username, email address, or service-principal client ID used to authenticate with the control plane.

Syntax

Uid=<username>

Description

## Required (with one of `Pwd`, `Token`, or a stored credential) `Uid=` identifies the user the driver authenticates as. Combined with `Pwd=` (password), `Token=` (bearer), or a stored credential in the OS keychain, it forms a complete authentication request. ## Format The driver sends `Uid=` to the control plane untouched. The control plane's auth provider chooses how to interpret it; supply the value in whatever form your provider expects (email, username, account ID). ## Aliases The parser also accepts `User=` and `User ID=` as alternative spellings for compatibility with connection strings copied from SQL Server tooling. They map to the native `Uid=` key. ## Interaction with credential storage When `Pwd=` is omitted, the driver looks up `Pwd:<Uid>` in the OS secret store under the DSN namespace. Two DSNs with the same `Uid` but different stored secrets are kept distinct because the lookup is namespaced by DSN name; see `ODBC_CRED_STORE`.

Parameters

Name	Type	Description
Uid		The user identity to authenticate as. Format depends on the auth provider: an email for human users, a UUID-like client ID for service principals, or a username for legacy directories. The driver does not transform this value; it is passed verbatim to the control plane.

Examples

Uid=alice@example.com

Uid=svc-etl-prod-001

Pitfalls

• Email addresses with `+` suffix (e.g. `alice+ci@example.com`) are valid as long as the auth provider accepts the form. The driver does not URL-encode the value.
• Whitespace around `=` is significant in some hand-written `odbc.ini` files. `Uid =alice` (with a leading space in the value) is a different identity than `Uid=alice` to most auth providers. Strip whitespace when copy-pasting from documentation.

See Also

• ODBC_CONN_PWD
• ODBC_CONN_TOKEN
• ODBC_CONN_AUTHMODE
• ODBC_CRED_STORE
• ODBC_TS_AUTH_FAILURES