awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-10-07 00:27:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #4180 from Infisical/daniel/tls-auth-docs

Browse Source 
docs: document use of port 8433 for TLS certificate auth
This commit is contained in:
Daniel Hougaard
2025-07-17 00:45:08 +04:00
committed by GitHub
parent fdaf8f9a87 32b2f7b0fe
commit 6ce6c276cd
2 changed files with 12 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api-reference/endpoints/tls-cert-auth/login.mdx
+5
View File
@@ -2,3 +2,8 @@
title: "Login" title: "Login"
openapi: "POST /api/v1/auth/tls-cert-auth/login" openapi: "POST /api/v1/auth/tls-cert-auth/login"
--- ---
<Warning>
Infisical US/EU and dedicated instances are deployed with AWS ALB. TLS Certificate Auth must flow through our ALB mTLS pass-through in order to authenticate.
When you are authenticating with TLS Certificate Auth, you must use the port `8443` instead of the default `443`. Example: `https://app.infisical.com:8443/api/v1/auth/tls-cert-auth/login`
</Warning>
docs/documentation/platform/identities/tls-cert-auth.mdx
+7 -3
View File
@@ -42,10 +42,14 @@ To be more specific:
Most of the time, the Infisical server will be behind a load balancer or Most of the time, the Infisical server will be behind a load balancer or
proxy. To propagate the TLS certificate from the load balancer to the proxy. To propagate the TLS certificate from the load balancer to the
instance, you can configure the TLS to send the client certificate as a header instance, you can configure the TLS to send the client certificate as a header
that is set as an [environment that is set as an [environment variable](/self-hosting/configuration/envars#param-identity-tls-cert-auth-client-certificate-header-key).
variable](/self-hosting/configuration/envars#param-identity-tls-cert-auth-client-certificate-header-key).
</Accordion> </Accordion>
<Note>
Infisical US/EU and dedicated instances are deployed with AWS ALB. TLS Certificate Auth must flow through our ALB mTLS pass-through in order to authenticate.
When you are authenticating with TLS Certificate Auth, you must use the port `8443` instead of the default `443`. Example: `https://app.infisical.com:8443/api/v1/auth/tls-cert-auth/login`
</Note>
## Guide ## Guide
In the following steps, we explore how to create and use identities for your workloads and applications on TLS Certificate to In the following steps, we explore how to create and use identities for your workloads and applications on TLS Certificate to
@@ -123,7 +127,7 @@ try {
const clientCertificate = fs.readFileSync("client-cert.pem", "utf8"); const clientCertificate = fs.readFileSync("client-cert.pem", "utf8");
const clientKeyCertificate = fs.readFileSync("client-key.pem", "utf8"); const clientKeyCertificate = fs.readFileSync("client-key.pem", "utf8");
const infisicalUrl = "https://app.infisical.com"; // or your self-hosted Infisical URL const infisicalUrl = "https://app.infisical.com:8443"; // or your self-hosted Infisical URL
const identityId = "<your-identity-id>"; const identityId = "<your-identity-id>";
// Create HTTPS agent with client certificate and key // Create HTTPS agent with client certificate and key