Clientauth for services
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
This is more a feature request than an issue.
I know it is possible to use client certificate base authentication within OpenShift, for example while logging into the console or using the API endpoint.
What I am trying to achieve is the use of clientauth for services. I know it is possible to tell OpenShift to pass SSL connections to the pods and have them do the ssl handshake and - if needed - client certificate authentication. But this involves setting up the whole thing inside the pods.
In my scenario this would mean setting up a haproxy that does the job inside the container. From my point of view it would be better if "the platform" could handle this.
I have seen that it is possible to deploy customized routers to OpenShift, but I found no way of setting up haproxy specific configuration for handling clientauth in the templates that are there for set up.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the customized router and HAProxy configuration templates mentioned in the issue, and trace how TLS connections are passed to services or pods. Define the configuration and termination behavior needed for client-certificate authentication; done requires an agreed platform-level design and validation path, which the issue does not currently specify.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100