Skip to content

Commit 382f7fb

Browse files
committed
fix(docs): update simstudio.ai URLs to sim.ai in SSO docs
1 parent c2529c3 commit 382f7fb

1 file changed

Lines changed: 11 additions & 11 deletions

File tree

  • apps/docs/content/docs/en/enterprise

apps/docs/content/docs/en/enterprise/sso.mdx

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -62,15 +62,15 @@ The **Callback URL** shown in the form is the endpoint your identity provider mu
6262

6363
**OIDC providers** (Okta, Microsoft Entra ID, Google Workspace, Auth0):
6464
```
65-
https://simstudio.ai/api/auth/sso/callback/{provider-id}
65+
https://sim.ai/api/auth/sso/callback/{provider-id}
6666
```
6767

6868
**SAML providers** (ADFS, Shibboleth):
6969
```
70-
https://simstudio.ai/api/auth/sso/saml2/callback/{provider-id}
70+
https://sim.ai/api/auth/sso/saml2/callback/{provider-id}
7171
```
7272

73-
For self-hosted, replace `simstudio.ai` with your instance hostname.
73+
For self-hosted, replace `sim.ai` with your instance hostname.
7474

7575
### 5. Save and test
7676

@@ -92,7 +92,7 @@ Click **Save**. To test, sign out and use the **Sign in with SSO** button on the
9292
2. Select **OIDC - OpenID Connect**, then **Web Application**
9393
3. Set the **Sign-in redirect URI** to your Sim callback URL:
9494
```
95-
https://simstudio.ai/api/auth/sso/callback/okta
95+
https://sim.ai/api/auth/sso/callback/okta
9696
```
9797
4. Under **Assignments**, grant access to the relevant users or groups
9898
5. Copy the **Client ID** and **Client Secret** from the app's **General** tab
@@ -124,7 +124,7 @@ Click **Save**. To test, sign out and use the **Sign in with SSO** button on the
124124
1. Go to **Microsoft Entra ID → App registrations → New registration**
125125
2. Under **Redirect URI**, select **Web** and enter your Sim callback URL:
126126
```
127-
https://simstudio.ai/api/auth/sso/callback/azure-ad
127+
https://sim.ai/api/auth/sso/callback/azure-ad
128128
```
129129
3. After registration, go to **Certificates & secrets → New client secret** and copy the value immediately — it won't be shown again
130130
4. Go to **Overview** and copy the **Application (client) ID** and **Directory (tenant) ID**
@@ -156,7 +156,7 @@ Click **Save**. To test, sign out and use the **Sign in with SSO** button on the
156156
2. Set the application type to **Web application**
157157
3. Add your Sim callback URL to **Authorized redirect URIs**:
158158
```
159-
https://simstudio.ai/api/auth/sso/callback/google-workspace
159+
https://sim.ai/api/auth/sso/callback/google-workspace
160160
```
161161
4. Copy the **Client ID** and **Client Secret**
162162

@@ -187,12 +187,12 @@ Click **Save**. To test, sign out and use the **Sign in with SSO** button on the
187187
2. Choose **Claims aware**, then **Enter data about the relying party manually**
188188
3. Set the **Relying party identifier** (Entity ID) to your Sim base URL:
189189
```
190-
https://simstudio.ai
190+
https://sim.ai
191191
```
192192
For self-hosted, use your instance's base URL (e.g. `https://sim.company.com`)
193193
4. Add an endpoint: **SAML Assertion Consumer Service** (HTTP POST) with the URL:
194194
```
195-
https://simstudio.ai/api/auth/sso/saml2/callback/adfs
195+
https://sim.ai/api/auth/sso/saml2/callback/adfs
196196
```
197197
For self-hosted: `https://sim.company.com/api/auth/sso/saml2/callback/adfs`
198198
5. Export the **Token-signing certificate** from **Certificates**: right-click**View CertificateDetailsCopy to File**, choose **Base-64 encoded X.509 (.CER)**. The `.cer` file is PEM-encodedrename it to `.pem` before pasting its contents into Sim.
@@ -204,7 +204,7 @@ Click **Save**. To test, sign out and use the **Sign in with SSO** button on the
204204
|-------|-------|
205205
| Provider Type | SAML |
206206
| Provider ID | `adfs` |
207-
| Issuer URL | `https://simstudio.ai` |
207+
| Issuer URL | `https://sim.ai` |
208208
| Domain | `company.com` |
209209
| Entry Point URL | `https://adfs.company.com/adfs/ls` |
210210
| Certificate | Contents of the `.pem` file |
@@ -223,7 +223,7 @@ Click **Save**. To test, sign out and use the **Sign in with SSO** button on the
223223

224224
Once SSO is configured, users with your domain (`company.com`) can sign in through your identity provider:
225225

226-
1. User goes to `simstudio.ai` and clicks **Sign in with SSO**
226+
1. User goes to `sim.ai` and clicks **Sign in with SSO**
227227
2. They enter their work email (e.g. `alice@company.com`)
228228
3. Sim redirects them to your identity provider
229229
4. After authenticating, they are returned to Sim and added to your organization automatically
@@ -268,7 +268,7 @@ Users who sign in via SSO for the first time are automatically provisioned and a
268268
},
269269
{
270270
question: "What is the Callback URL?",
271-
answer: "The Callback URL (also called Redirect URI or ACS URL) is the endpoint in Sim that receives the authentication response from your identity provider. For OIDC providers it follows the format: https://simstudio.ai/api/auth/sso/callback/{provider-id}. For SAML providers it is: https://simstudio.ai/api/auth/sso/saml2/callback/{provider-id}. You must register this URL in your identity provider before SSO will work."
271+
answer: "The Callback URL (also called Redirect URI or ACS URL) is the endpoint in Sim that receives the authentication response from your identity provider. For OIDC providers it follows the format: https://sim.ai/api/auth/sso/callback/{provider-id}. For SAML providers it is: https://sim.ai/api/auth/sso/saml2/callback/{provider-id}. You must register this URL in your identity provider before SSO will work."
272272
},
273273
{
274274
question: "How do I update or replace an existing SSO configuration?",

0 commit comments

Comments
 (0)