Configuring Authentication on Non-Windows Machines

To access data from Athena, you must authenticate the connection. You can configure the Simba Athena ODBC Driver to provide your credentials and authenticate the connection using one of the following methods:

• Using the Default Credentials Provider Chain on Non-Windows Machines
• Using IAM Credentials on Non-Windows Machines
• Using an IAM Profile on Non-Windows Machines
• Using the Browser SSO OIDC Credentials Provider for IAM Identity Center
• Using an Instance Profile on Non-Windows Machines
• Using the Active Directory Federation Services (AD FS) Credentials Provider on a Non-Windows Machine
• Using the Azure AD Credentials Provider on a Non-Windows Machine
• Using the Browser Azure AD Credentials Provider on a Non-Windows Machine
• Using a Browser Plugin for a SAML Service on a Non-Windows Machine
• Using a JSON Web Token (JWT)
• Using the JWT_TIP Credentials Provider for IAM Identity Center
• Using the Okta Service on a non-Windows machine
• Using Okta MFA with Okta Verify on a non-Windows machine
• Using Okta MFA with Google Authenticator on a non-Windows machine
• Using Okta MFA with SMS Authentication on a non-Windows machine
• Using PingFederate Service
• Using an External Credentials Service
• Using DataZone IAM Credentials Provider on a Non-Windows Machine
• Using DataZone IDC Credentials Provider on a Non-Windows Machine

You can set the connection properties described below in a connection string or in a DSN (in the odbc.ini file). Settings in the connection string take precedence over settings in the DSN.