Co-Auth: Documentation
WebsiteDocumentaionGithub
  • 🏠Welcome to Co-Auth Documentation
  • Getting Started
    • Co-Auth Modules & Release Status
      • Time Based OTP
      • Reconfirm
    • Architecture
      • Components Flow
      • Integration Overview
        • Integration with Co-Auth
      • Tech Stack
    • Requirements & Prerequisites
    • Installation
      • Setup as a Test / Dev environment
        • Test Setup on Red Hat OpenShift
        • Test Setup on Kubernetes
        • Cloud Provider
        • Development Setup
      • Setup on Production
  • using COAUTH
    • 🕐Key Concepts
  • API
    • 🕐Overview
    • 🕐API Documentation
  • Advanced Topics
    • Customization
      • Database
      • 🕐Caching
      • Good to Have
  • contribute to CoAuth
    • Contribute
    • Setup a Build Environment
  • Usecases
    • 🙂Articles
    • Implementation Use Case
      • 🕐2nd Factor for Authentication
      • 🕐Securing Internal Pages
      • 🕐Transaction verification
      • 🕐Safeguard from MTM, Keystroke attacks
      • 🕐QR are not just for Login
  • administration
    • 🕐Coming Soon
  • Group 1
    • Behind the Scenes
      • Sponsors
      • Adopters
      • Core Contributors
Powered by GitBook
On this page
  • External Load balancer
  • Istio Service mesh
  • ELK for Log Collection and Aggregation

Was this helpful?

  1. Advanced Topics
  2. Customization

Good to Have

These are good to have components that can save an organization from Nightmare while debugging issues

External Load balancer

Its best that Co-Auth exists in private subnet and the request come onto a public subnet, where you can place a load balancer.

Istio Service mesh

  1. Tracing

  2. Controlling releases

  3. Communication between microservices

  4. Monitoring health of pods

ELK for Log Collection and Aggregation

Would enable logging to a central location

PreviousCachingNextContribute

Last updated 1 year ago

Was this helpful?