Skip to content

Commit 7c9eb66

Browse files
committed
Run pnpm format
1 parent 7cd308a commit 7c9eb66

File tree

1 file changed

+17
-16
lines changed
  • docs/authentication/enterprise-connections/saml

1 file changed

+17
-16
lines changed

docs/authentication/enterprise-connections/saml/azure.mdx

Lines changed: 17 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,9 @@ This process requires configuration changes in both the Clerk Dashboard, and in
5050
You are welcome the use the below email template with detailed instructions. They contain the following
5151
template strings that you should replace with your actual values:
5252

53-
- [YOUR_APPLICATION_NAME]
54-
- [YOUR_CLERK_ENTITY_ID]
55-
- [YOUR_CLERK_REPLY_URL]
53+
- \[YOUR\_APPLICATION\_NAME]
54+
- \[YOUR\_CLERK\_ENTITY\_ID]
55+
- \[YOUR\_CLERK\_REPLY\_URL]
5656

5757
<Copyable as="html">
5858
Here are the instructions for setting up SAML SSO with Microsoft Azure Entra ID:
@@ -64,9 +64,9 @@ This process requires configuration changes in both the Clerk Dashboard, and in
6464
1. Select **New application**. You'll be redirected to the **Browse Microsoft Entra Gallery** page.
6565
1. Select **Create your own application**.
6666
1. In the modal that opens:
67-
- **Name** of your application (likely [YOUR_APPLICATION_NAME]).
68-
- Select **Integrate any other application you don't find in the gallery (Non-gallery)**.
69-
- Select **Create**.
67+
- **Name** of your application (likely \[YOUR\_APPLICATION\_NAME]).
68+
- Select **Integrate any other application you don't find in the gallery (Non-gallery)**.
69+
- Select **Create**.
7070

7171
**Step 2: Assign your users or groups in Microsoft**
7272

@@ -87,24 +87,27 @@ This process requires configuration changes in both the Clerk Dashboard, and in
8787
1. Select **Edit**. The **Basic SAML Configuration** panel will open.
8888
1. Add the following **Identifier (Entity ID)** and **Reply URL (Assertion Consumer Service URL)** values. These values will be saved automatically.
8989
- **Identifier (Entity ID)**: `[YOUR_CLERK_ENTITY_ID]`
90-
- **Reply URL (Assertion Consumer Service URL)**: `[YOUR_CLERK_REPLY_URL]`
90+
- **Reply URL (Assertion Consumer Service URL)**: `[YOUR_CLERK_REPLY_URL]`
9191
1. Select **Save** at the top of the panel. Close the panel.
9292

9393
**Step 4: Verify correct configuration of attributes and claims**
9494

9595
We expect your SAML responses to have the following specific attributes:
9696

9797
Email address (required). This is the email address that your users will use to authenticate into your app:
98-
- Claim name: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`
99-
- Value: `user.mail`
98+
99+
- Claim name: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`
100+
- Value: `user.mail`
100101

101102
First name (optional):
102-
- Claim name: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname`
103-
- Value: `user.givenname`
103+
104+
- Claim name: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname`
105+
- Value: `user.givenname`
104106

105107
First name (optional):
106-
- Claim name: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname`
107-
- Value: `user.surname`
108+
109+
- Claim name: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname`
110+
- Value: `user.surname`
108111

109112
These are the defaults, and probably won't need you to change them. However, many SAML configuration errors are due to incorrect attribute mappings, so it's worth double-checking. Here's how:
110113

@@ -116,14 +119,13 @@ This process requires configuration changes in both the Clerk Dashboard, and in
116119

117120
1. Still on the **Set up Single Sign-On with SAML** page, find the **SAML Certificates** section.
118121
1. Copy the **App Federation Metadata Url**, and reply to this email with it. This is the final piece of information we need to enable SAML.
119-
120122
</Copyable>
121123

122124
## Add App Federation Metadata URL in the Dashboard
123125

124126
After following the instructions in the email, your customer should have sent you the Microsoft app's **App Federation Metadata URL**. Now, you're going to add it to the Clerk connection, completing the SAML connection configuration.
125127

126-
1. Navigate to the [**SSO connections**](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) page in the Clerk Dashboard.
128+
1. Navigate to the [**SSO connections**](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) page in the Clerk Dashboard.
127129
1. Select the SAML connection.
128130
1. In the **Identity Provider Configuration** section, under **App Federation Metadata Url**, paste the **App Federation Metadata URL**.
129131
1. Select **Fetch & save**.
@@ -139,5 +141,4 @@ This process requires configuration changes in both the Clerk Dashboard, and in
139141

140142
1. Navigate back to the Clerk Dashboard where you should still have the connection's configuration page open. If not, navigate to the [**SSO connections**](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) page and select the connection.
141143
1. At the top of the page, toggle on **Enable connection** and select **Save**.
142-
143144
</Steps>

0 commit comments

Comments
 (0)