Does iDBQuery support MFA and two-factor authentication?
Yes. iDBQuery supports multi-factor authentication, and when you sign in through your own identity provider it enforces whatever MFA and conditional-access policies you already run, such as authenticator apps, hardware keys, or push approval. This keeps a stolen password alone from granting access to your data.
Multi-factor authentication adds a second proof of identity beyond a password, and iDBQuery is built to honour the MFA you already require.
- Through your IdP - when you connect Okta, Microsoft Entra, or Google Workspace via SSO, sign-in inherits their MFA, so authenticator apps, FIDO2 hardware keys, and push approvals all apply.
- Conditional access - policies like 'require MFA off the corporate network' or 'block risky sign-ins' are enforced by your provider before iDBQuery is ever reached.
- Consistent everywhere - the same login controls apply whether iDBQuery runs in the cloud, your VPC, or on-prem against your internal identity system.
For example, an analyst working from home is prompted for a hardware-key tap by your identity provider before iDBQuery loads any data. MFA guards the door, but iDBQuery's architecture is what limits the blast radius behind it: data is queried in place rather than exported, RBAC scopes what each user can see, and traffic is encrypted in transit with data encrypted at rest. Even a compromised credential is contained by these layers. If you do not yet use an external identity provider, talk to us about the authentication options that fit your deployment.
Updated 2026-06-22