authgear / authgear/authgear-server

[Feature Request] TLS termination within server

Open
#179 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2k
Forks
125
Avg merge
2d 17h
Merged PRs (30d)
32

Description

In very strict security setup, we may want to ensure all traffic are encrypted in transit. Including communications between authgear and application or ingress controller.

We can enable k8s ingress controller with https backend:
https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#backend-protocol

or SSL passthrough:
https://kubernetes.github.io/ingress-nginx/user-guide/tls/#ssl-passthrough

typical setup:
```
--https--> k8s-ingress --https--> authgear
--https--> k8s-ingress --https--> application --https--> authgear
--https--> k8s-ingress --https--> application ----https----> k8s-ingress --https--> authgear
```

Optionally, supports mTLS.

Contributor guide

Open the contributing guide

Research direction

No repository file, test, or entry point is named. Start by locating the server's listener and TLS configuration, then review the referenced Kubernetes ingress backend-protocol and SSL passthrough documentation. Done should include encrypted server communication and a defined approach for the optional mTLS support, with tests covering the resulting behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend, infrastructure, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.