Current for Security Teams
Self-host on your own infrastructure with short-lived tokens, scope-based authorization, and role-scoped access.
Pain points
- Long-lived credentials are a standing risk
- Access decisions should be based on explicit scopes, not assumed role trust
- Link and analytics data should not have to leave your own infrastructure
- Certificate lifecycle management needs to be auditable, not manual
How Current helps
- Short-lived (30 min) access tokens with rotating (7-day) refresh tokens limit exposure. (JWT Authentication)
- Every permission check resolves to an explicit OAuth2-style scope, not a role name. (Role-Based Access Control)
- Centralize authentication through your existing enterprise identity provider. (OIDC / SSO)
- Manage TLS certificate requests and renewal through admin-scoped API endpoints. (Certificate Management)