Does iDBQuery support single sign-on with Okta?
Yes. iDBQuery supports single sign-on with Okta over SAML 2.0 and OpenID Connect, so your team signs in with existing Okta credentials and access follows your identity provider. Combined with role-based access control, Okta then governs who can reach which projects and data inside iDBQuery.
iDBQuery connects to Okta the way other enterprise apps do, so you manage access from one place instead of maintaining a separate user list.
- Standard protocols - sign-in works over SAML 2.0 or OpenID Connect, so Okta handles authentication and iDBQuery never stores a separate password.
- Access follows identity - when you disable a user in Okta, their iDBQuery access ends, so there are no orphaned accounts to chase.
- Roles map to groups - Okta group membership can drive iDBQuery roles, so finance sees finance projects and analysts see theirs, all enforced by role-based access control.
- Any deployment - in the cloud, your own VPC, or a fully air-gapped install, iDBQuery points at whichever Okta or internal identity endpoint you already run, keeping authentication inside your boundary.
For example, a controller added to your Okta 'Finance' group is signed straight into the finance workspace with the right permissions, and revoking that group membership removes access instantly. Because iDBQuery leads with architecture - query-in-place, RBAC, and encryption in transit and at rest - SSO is one control layer on top of a design that keeps your data in your walls. Ask us for the exact SAML or OIDC setup details for your Okta tenant.
Updated 2026-06-22