Skip to content

Commit e1c4974

Browse files
committed
update saml/scim dos
1 parent e31dc56 commit e1c4974

File tree

3 files changed

+17
-4
lines changed

3 files changed

+17
-4
lines changed
Loading

docs/misc/14_saml_and_scim/index.md

Lines changed: 17 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,17 @@ ACS Url is `<instance_url>/api/saml/acs`
1010
SCIM connector is `<instance_url>/api/scim`
1111
Application username format is `Email`
1212

13-
Pass SAML_METADATA containing the metadata URL to the server containers to enable SAML authentication. In the helm charts, the value is `enterprise.samlMetadata`
13+
![Instance Settings UI](instance_settings.png)
14+
In the Instance Settings UI, pass the SAML Metadata URL (or content) containing the metadata URL (or XML content).
1415

1516
### Okta
1617

1718
Configure Okta with the following settings (and replace cf.wimill.xyz with your domain):
1819

1920
![Okta settings](./okta.png.webp)
2021

21-
Pass SAML_METADATA containing the metadata URL to the server containers to enable SAML authentication. In the helm charts, the value is `enterprise.samlMetadata`:
22+
![Instance Settings UI](instance_settings.png)
23+
In the Instance Settings UI, pass the SAML Metadata URL (or content) containing the metadata URL (or XML content).
2224

2325
![Okta Metadata URL](./okta2.png.webp)
2426

@@ -54,7 +56,8 @@ Configure Okta with the following settings (and replace cf.wimill.xyz with your
5456

5557
![Okta SCIM](okta-scim1.png.webp)
5658

57-
For the Bearer Token, use the value of `enterprise.scimToken` in the helm charts which corresponds to the `SCIM_TOKEN`` env variable for the server container.
59+
![Instance Settings UI](instance_settings.png)
60+
In the Instance Settings UI, set the SCIM token containing the secret value that you will share to Okta.
5861

5962
![Okta SCIM](okta-scim.png.webp)
6063

@@ -64,7 +67,17 @@ Create an application from the "Enterprise Applications" menu (see [Configuring
6467

6568
![Azure SCIM](azure-scim-new_application.png)
6669

67-
Choose the "Automatic" provisioning mode, and then for the Tenant URL, input the public URL of your Windmill server with the prefix `/api/scim`. For the Secret Token, use the value of `enterprise.scimToken` in the helm charts which corresponds to the `SCIM_TOKEN` env variable for the server container. You can then click on the Test Connection button to validate Azure can connect to Windmill's SCIM endpoint. You can then choose to sync only the Users and Groups assigned to this application, or all users and groups. Note that if you choose the former, after you save, go to the application's page and click on the "Users and groups" button in the left menu bar. Only the users and groups present here will be synced to Windmill.
70+
Choose the "Automatic" provisioning mode, and then for the Tenant URL, input the public URL of your Windmill server with the prefix `/api/scim`.
71+
72+
![Azure SAML metadata](azure_saml_metadata.png)
73+
74+
Copy the App Federation Metadata URL and paste it in the Instance Settings UI.
75+
76+
![Instance Settings UI](instance_settings.png)
77+
78+
In the Instance Settings UI, set the SCIM token containing the secret value that you will share to Azure. You can click "Test" in Windmill's Instance Settings UI to validate the SAML metadata URL/Content.
79+
80+
You can then click on the Test Connection button to validate Azure can connect to Windmill's SCIM endpoint. You can then choose to sync only the Users and Groups assigned to this application, or all users and groups. Note that if you choose the former, after you save, go to the application's page and click on the "Users and groups" button in the left menu bar. Only the users and groups present here will be synced to Windmill.
6881

6982
![Azure SCIM](azure-scim-application_provisioning.png)
7083

docs/misc/14_saml_and_scim/instance_settings.png

Loading

0 commit comments

Comments
 (0)