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

Was this helpful?

  1. Getting Started

Requirements & Prerequisites

How to host Co-Auth on your infrastructure

Cloud First

Co-Auth is designed as as cloud first application. Meaning you need containerized environment for running Co-Auth

  • Co-Auth consists of multiple microservices

  • One or Many Postgres instance for persistent storage (depending on how you want your database i.e. tables spread in separate database as per microservice dependency or a single database)

  • Kafka for event streaming across microservices communication, logging, notification

  • Infinispan in-memory cache to help reduce operations on database

  • Kamelets for notifications

  • Istio, ELK (in upcoming releases)

PreviousTech StackNextInstallation

Last updated 1 year ago

Was this helpful?