- IMAPI Angular service: https://github.com/Kolman-Freecss/kf-imapi-angular
- IMAPI Incident Service: https://github.com/Kolman-Freecss/kf-imapi-incident-service
- IMAPI Response Team Service: https://github.com/Kolman-Freecss/kf-imapi-response-service
- IMAPI Notification Service: https://github.com/Kolman-Freecss/kf-imapi-notification-service
- IMAPI Authentication Gateway Service: https://github.com/Kolman-Freecss/kf-imapi-auth-gateway
- IMAPI DevOps / Kafka Event Handling: https://github.com/Kolman-Freecss/kf-imapi-devops
- Prometheus: http://localhost:9090
- Grafana: http://localhost:3000
- Zipkin: http://localhost:9411
- Keycloak: http://localhost:8080
- Eureka: http://localhost:8761
Auth Gateway Service for IMAPI (Incident Management API) project:
Features:
- Implementation of security using Spring Boot 3.0 and Keycloak with JSON Web Tokens (JWT).
- API Gateway for routing requests to the appropriate service.
- Circuit Breaker using Resilience4j.
- Also we hide the internal services from the outside world and KEYCLOAK (everything is behind the gateway).
- SSO (Single Sign-On) using Keycloak.
- OAuth2 Protocol.
- Internal JWT signing to validate the token in every microservice verifying the authenticity of the API Gateway token. (X-Internal-Auth)
- (Another robust option is to sign every token through TLS, but it is not implemented in this project).
- Spring Boot 3.0
- Keycloak
- Kafka
- Maven
- Docker
- Spring Cloud Netflix (Eureka)
- Observability - Micrometer Tracing and Zipkin (Distributed Tracing) (Sleuth is deprecated)
- We use AOP support to decorate the methods with tracing annotations.
- Prometheus and Grafana (Monitoring)
- Redis (Caching)
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.