A detailed architecture of components


API Gateway

Routing to all Co-Auth resources takes place throught this gateway. Injecting application details by calling auth guard service

Auth Guard

A microservice acting as filter called for API keys validation. it is also responsible for providing app details to down stream services

Module Registry

This microservice is responsible to act as first level initiator, if a user for an application is registered for the type of requested auth. It also holds the status of completion


These are microservices segregated based on the type of auth method they handle


The relational database to maintain the application data. By design no database level relations are maintained which further allows microservices to run their own database in future


Used to store in memory on cluster data, so that pods can share the data and avoid making DB calls, as they scale up and down


Vuejs based web plugin that can be embedded by thrid party applications within a iframe. Used in self-onboarding and verification sections.

Management UI

A Mock UI concept based on Vuejs to idea the features in the administration panel.

Kafka / AMQ

  1. Log all transactions and activities to Kafka which can be used to send notifications to users of actions (coming soon)

Kafka sinks / consumers

For complex applications we will have Quarkus serverless implementation of consumers and for others we have the Kamelets sinks which provide out of the box integration

Last updated