Can I set session timeout and login policies in iDBQuery?
Yes. iDBQuery supports configurable session policies such as idle and absolute timeouts, and when you sign in through your identity provider it also honours that provider's session lifetime, re-authentication, and conditional-access rules. This lets you enforce how long a session lasts and when users must sign in again.
Session and login policies control how long access stays valid and when someone has to prove their identity again.
- Timeouts - set idle and maximum session lengths so an unattended session expires rather than staying open indefinitely.
- IdP-driven - when SSO is enabled, your provider's session lifetime, step-up authentication, and conditional-access rules govern re-authentication, so iDBQuery stays consistent with the rest of your stack.
- Sign-out and revocation - administrators can end sessions, and disabling a user in your directory cuts their access.
For example, you might require re-authentication every eight hours and immediate sign-out after 30 minutes idle, so a laptop left open on a trading floor does not remain a live window into your data. These controls sit on top of iDBQuery's core protections rather than replacing them: data is queried in place, every figure is cited to its source, RBAC limits what a session can reach, and traffic is encrypted. Tight session policy narrows the window of exposure if a device is lost, while the architecture limits what that session could ever have accessed. Ask us which session controls apply to your deployment and identity provider.
Updated 2026-06-22