awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-09-22 13:39:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

addressed requested changes

Browse Source
This commit is contained in:
Daniel Hougaard
2025-11-07 05:45:51 +04:00
parent 53951c57bd
commit 542f823771
6 changed files with 25 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/integrations/app-connections/azure-client-secrets.mdx
View File

@@ -122,7 +122,7 @@ Infisical currently only supports two methods for connecting to Azure, which are
![Upload certificate](/images/app-connections/azure/client-secrets/upload-certificate.png)
<Tip>
Keep in mind that you'll need the both the certificate & private key in order to configure the Azure Client Secrets connection within Infisical.
Keep in mind that both the certificate and its private key are required to configure the Azure Client Secrets connection in Infisical.
</Tip>
</Step>
</Steps>
@@ -168,7 +168,7 @@ Infisical currently only supports two methods for connecting to Azure, which are
</Tab>
<Tab title="Certificate">
<Step title="Create Connection">
Fill in the **Tenant ID**, **Client ID**, **Certificate**, and **Private Key** fields with the Directory (Tenant) ID, Application (Client) ID, Certificate and Private Key you obtained in the [previous step](#certificate-authentication).
Fill in the **Tenant ID**, **Client ID**, **Certificate (PEM format)**, and **Private Key** fields with the Directory (Tenant) ID, Application (Client) ID, Certificate and Private Key you obtained in the [previous step](#certificate-authentication).
<Tip>
The private key is never transmitted to Azure, and it is only used to sign the client assertion used to authenticate with Azure.