Picture the moment your data protection workflow tangles into several half-documented APIs, identity rules pulled from multiple vaults, and access logs that only make sense to their author. This is where Cohesity Jetty earns its keep. It brings structure and control to the wild west of backup management, giving teams one engine for secure, auditable access to infrastructure data.
Cohesity handles your data at scale: snapshotting workloads, deduplicating storage, and delivering a unified recovery platform. Jetty is the layer that orchestrates communication between the UI, the APIs, and the underlying services. It manages sessions, tokens, and user requests. Together, they create a safe gate rather than a loose collection of doors, which is exactly what infrastructure teams crave in large multi-tenant environments.
At setup, Cohesity Jetty works like a broker. It receives incoming requests, authenticates them via SSO or OIDC-compatible identity providers such as Okta or AWS IAM Identity Center, then directs traffic to the right module within Cohesity’s architecture. Each service runs insulated from the next, which limits blast radius and simplifies compliance reviews like SOC 2 or ISO 27001 checks. The result is clean request routing and traceable operations.
If you are integrating Jetty into an existing automation stack, start with strict RBAC mapping. Tie user groups to policies at the identity level, not at each service node. Rotate secrets on a schedule using your existing vault or key management system. When something fails, use Jetty’s request logs to trace the session flow instead of guessing which microservice timed out. Practical debugging beats blind restarts every time.
Key benefits:
- Centralizes authentication and authorization for all Cohesity components.
- Enables granular auditing for every operation, ideal for regulated environments.
- Improves stability through consistent connection pooling and request throttling.
- Reduces operator error by relying on token-based access instead of manual credentials.
- Speeds up compliance validation with uniform security policies across environments.
For developers, Jetty means fewer places to log in or request approval just to test a workflow. CI/CD pipelines run faster because identity checks are automated and cached. Deployment scripts stop waiting on humans, and debugging becomes a predictable part of the day rather than an emergency.
Platforms like hoop.dev turn those access rules into guardrails that enforce policy automatically. Instead of chasing ephemeral credentials, your engineers get an identity-aware proxy that knows who’s calling what and when. That’s the difference between chasing stability and living in it.
How do I connect Cohesity Jetty to my identity provider?
Use OIDC or SAML configuration with your chosen provider. Map roles to provider groups, verify token lifetimes match your session policy, and enable auditing. Once configured, Jetty authenticates requests transparently while preserving full traceability.
When should I scale Jetty instances?
Scale out when request latency spikes or when new workloads trigger concurrent authentication calls. More Jetty nodes distribute the connection load and maintain consistent response times.
Cohesity Jetty is less about software complexity and more about predictability. When it’s tuned correctly, your infrastructure runs like a cleanly governed conversation instead of a shouting match between services.
See an Environment Agnostic Identity-Aware Proxy in action with hoop.dev. Deploy it, connect your identity provider, and watch it protect your endpoints everywhere—live in minutes.