Skip to main content

Operational Notes

Runtime posture​

WispHive serves production documentation at the root URL and exposes only the externally supported OAuth integration APIs and callback contracts documented in this portal.

Privacy policy​

  • AAA handoff integrations must send only derived, non-sensitive identifiers.
  • Direct personally identifiable data such as raw email addresses, display names, or provider subjects must not be posted to WispHive callback endpoints.
  • WispHive uses per-entity derived identity namespaces and derived email domains to reduce privacy exposure while preserving session correlation.

Data policy​

  • OAuth client secrets, callback signing credentials, callback URLs, provider metadata, and persisted identity-related fields are encrypted at rest.
  • The encryption seed is derived from client id + security id + security token + service id, with AUTH_DATA_ENCRYPTION_KEY remaining the highest-priority override when explicitly supplied.
  • Callback payloads are reduced to operationally necessary derived identifiers and session references only.
  • Clients remain responsible for protecting upstream provider credentials and any raw user identity data retained in their own systems.

SLAs​

  • Redirect handoff URLs are short-lived and currently default to a 5-minute TTL.
  • AAA handoff callbacks are idempotent when the same Idempotency-Key is reused with the same payload.
  • WispHive expects client backends to retry transient callback failures with exponential backoff and jitter.
  • Integration partners should monitor callback failures, expired redirect usage, and invalid token usage as part of their production operations.

Operational expectations​

  • Keep OAuth client secrets in a secret manager.
  • Rotate AAA handoff API keys regularly from the dashboard.
  • Monitor failed callback attempts and invalid idempotency-key reuse.
  • Keep provider redirect URI settings synchronized with the current callback_url.