Skip to main content

Access Control

eCourtDate enforces layered access controls to ensure that only authorized users and systems can access agency data. This page covers authentication methods, multi-factor authentication, role-based permissions, and API access controls.

Authentication Methods​

MethodUse CaseDetails
API Keys (client_id / client_secret)Server-to-server API integrationOAuth 2.0 Client Credentials flow. See API Authentication.
OAuth / SSOConsole user login via identity providerSAML/OIDC with Azure AD, Google, Okta, and others. See OAuth / SSO.
SSH KeysSFTP file transfer authenticationKey-based authentication recommended. See SFTP Authentication.
Console LoginDirect Console accessEmail and password with mandatory MFA.

Multi-Factor Authentication​

MFA is mandatory for all Console user accounts. eCourtDate supports multiple MFA methods:

  • Authenticator apps: TOTP-based codes from apps such as Google Authenticator, Microsoft Authenticator, or Authy
  • Hardware security keys: FIDO2/WebAuthn devices (YubiKey and similar)
  • PIV/CAC smart cards: Personal Identity Verification and Common Access Card support for government users
  • IDP-enforced MFA: When using SSO, MFA is enforced at the identity provider level. See OAuth Security for details.

Role-Based Permissions​

eCourtDate uses granular, role-based access controls:

  • CRUD permissions: Create, Read, Update, and Delete permissions are assigned per record type
  • Agency-level assignment: Permissions are scoped to the agency, preventing cross-agency data access
  • Administrative roles: Separate roles for agency administrators, standard users, and read-only users
info

For a detailed permission matrix showing all record types and permission levels, contact the eCourtDate team through the Help Center.

API Access Controls​

API access is restricted through multiple mechanisms:

  • Agency-scoped clients: Each API client is bound to a specific agency. Cross-agency access is not possible through a single client.
  • IP allowlisting: API clients can be restricted to specific source IP addresses. Requests from unlisted IPs are rejected. See IP Allowlisting.
  • Token expiration: OAuth 2.0 access tokens expire and must be refreshed. See Token Lifecycle.
  • Separate credentials: Use separate API credentials for staging and production environments. See Environments.

Session Management​

info

For details on Console session timeout policies and concurrent session limits, contact the eCourtDate team through the Help Center.

Principle of Least Privilege​

Follow these guidelines to minimize unnecessary access:

  • Separate API clients per integration: Create dedicated API credentials for each system that connects to eCourtDate
  • Minimum permissions: Assign only the permissions each integration requires
  • Periodic access review: Review user accounts and API clients regularly; revoke access that is no longer needed
  • Rotate on personnel changes: When staff with access leave or change roles, rotate affected credentials. See Key Management.