Replies: 3 comments
-
Nothing has changed. EJBCA itself does not code any dependency on headers. |
Beta Was this translation helpful? Give feedback.
-
Looks like this might be possible now from ELB side: |
Beta Was this translation helpful? Give feedback.
-
I spoke too soon, I think. I am able to get the right header name, but I'm unable to get it to work directly because the ELB header is url encoded which WildFly does not seem to support. Reproduced this with nginx:
I've opened a WildFly enhancement. EDIT: I did end up having a small nginx container rewrite the header name and the contents with perl module (had to decode URL encoding and also add spaces on each line for the old multiline HTTP header support). Here is the
I used it with |
Beta Was this translation helpful? Give feedback.
-
Is
SSL_CLIENT_CERT
hardcoded somewhere in EJBCA? Is it possible to make it configurable?I'm interested in perhaps running EJBCA behind AWS Application Load Balancer which supports mTLS but passes the client certificate as
X-Amzn-Mtls-Clientcert
(per documentation).EDIT: After submitting this I found this thread on the old sourceforge site. Perhaps something has changed since then? Would rather avoid running an intermediate proxy to rewrite header name.
Beta Was this translation helpful? Give feedback.
All reactions