You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/manage/security/scim/about-scim-provisioning.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ See the following articles for directions to configure specific provisioning pro
20
20
21
21
### Create an access key
22
22
23
-
Before configuring a provisioning provider, you must create an [access key](/docs/manage/security/access-keys/) using a service account. This access key will provide authorization to provision users from the provider into Sumo Logic.
23
+
Before configuring a provisioning provider, create an [access key](/docs/manage/security/access-keys/) using a service account. This access key will provide authorization to provision users from the provider into Sumo Logic.
24
24
25
25
When you create the access key, copy its access ID and access key values. Depending on the provider you configure, you will enter these when you set up provisioning to use one of the following authorization methods:
Copy file name to clipboardExpand all lines: docs/manage/security/scim/provision-from-microsoft-entra-id.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ description: Learn how to provision users into Sumo Logic from Microsoft Entra I
7
7
8
8
import useBaseUrl from '@docusaurus/useBaseUrl';
9
9
10
-
This article describes how to provision users into Sumo Logic from Microsoft Entra ID (formerly Azure Active Directory).
10
+
This article describes how to provision users into Sumo Logic with Microsoft Entra ID (formerly Azure Active Directory).
11
11
12
12
## Prerequisites
13
13
@@ -17,11 +17,11 @@ Create an [access key](/docs/manage/security/access-keys/) using a service accou
17
17
18
18
When you create the access key, copy its access ID and access key values. You will enter these when you use [Base64 encoding](https://www.base64encode.org/) to Base64 encode `<access ID>:<access key>` to generate a token.
19
19
20
-
## Configure provisioning from Microsoft Entra ID
20
+
## Configure provisioning with Microsoft Entra ID
21
21
22
22
### Step 1: Create the app
23
23
24
-
1. Log in to Microsoft Azure.
24
+
1. Log in to [Microsoft Azure](http://portal.azure.com/) as an administrator.
25
25
1. Navigate to Microsoft Entra ID. (You can use the search bar to locate it.)
26
26
1. Navigate to **Manage > Enterprise Applications**.
Copy file name to clipboardExpand all lines: docs/manage/security/scim/provision-from-okta.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ description: Learn how to provision users into Sumo Logic from Okta.
7
7
8
8
import useBaseUrl from '@docusaurus/useBaseUrl';
9
9
10
-
This article describes how to provision users into Sumo Logic from Okta.
10
+
This article describes how to provision users into Sumo Logic with Okta.
11
11
12
12
## Prerequisites
13
13
@@ -27,7 +27,7 @@ If it is not already set up, [set up SAML for single sign-on with Okta](/docs/ma
27
27
28
28
<img src={useBaseUrl('img/security/provision-sumo-logic-saml-settings.png')} alt="ACS and entity ID from Sumo Logic" style={{border: '1px solid gray'}} width="800" />
29
29
30
-
## Configure provisioning from Okta
30
+
## Configure provisioning with Okta
31
31
32
32
### Step 1: Create the app
33
33
@@ -38,7 +38,7 @@ If it is not already set up, [set up SAML for single sign-on with Okta](/docs/ma
38
38
1. Enter the **Single sign-on URL** and **Audience URI (SP Entity ID)** for your Sumo Logic instance:<br/><img src={useBaseUrl('img/security/provision-okta-configure-saml.png')} alt="Configure SAML for the app" style={{border: '1px solid gray'}} width="600" /><br/>Obtain the single sign-on URL (Assertion Consumer URL) and entity ID from the SAML configuration of the Sumo Logic tenant where you will provision users (see [Prerequisites](#prerequisites)).<br/><img src={useBaseUrl('img/security/provision-sumo-logic-saml-settings.png')} alt="ACS and entity ID from Sumo Logic" style={{border: '1px solid gray'}} width="800" />
39
39
1. Click **Next** and click **Finish**. The app displays in Okta.<br/><img src={useBaseUrl('img/security/provision-okta-new-app.png')} alt="New app in Okta" style={{border: '1px solid gray'}} width="800" />
40
40
41
-
### Step 2: Configure provisioning
41
+
### Step 2: Set up provisioning
42
42
43
43
1. Configure the general settings for the app:
44
44
1. Click the **General** tab.
@@ -106,7 +106,7 @@ If it is not already set up, [set up SAML for single sign-on with Okta](/docs/ma
1. Navigate to **Applications > Applications** and select the app you created in Step 1.<br/><img src={useBaseUrl('img/security/provision-okta-new-app.png')} alt="New app in Okta" style={{border: '1px solid gray'}} width="800" />
112
112
1. Edit the attributes pushed from Okta to the provisioning app.
Copy file name to clipboardExpand all lines: docs/manage/security/scim/provision-from-onelogin.md
+117-1Lines changed: 117 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,4 +7,120 @@ description: Learn how to provision users into Sumo Logic from OneLogin.
7
7
8
8
import useBaseUrl from '@docusaurus/useBaseUrl';
9
9
10
-
This article describes how to provision users into Sumo Logic from OneLogin.
10
+
This article describes how to provision users into Sumo Logic with OneLogin.
11
+
12
+
## Prerequisites
13
+
14
+
### Create an access key
15
+
16
+
Create an [access key](/docs/manage/security/access-keys/) using a service account. This access key will provide authorization to provision users from OneLogin into Sumo Logic.
17
+
18
+
When you create the access key, copy its access ID and access key values. You will enter these when you use [Base64 encoding](https://www.base64encode.org/) to Base64 encode `<access ID>:<access key>` to generate a token.
19
+
20
+
## Configure provisioning with OneLogin
21
+
22
+
### Step 1: Create the app
23
+
24
+
1. Log in to your [OneLogin](https://www.onelogin.com/) account as an administrator.
1. Select **SCIM Provisioner with SAML (SCIM v2 Enterprise)**.
28
+
1. Change the **Display Name**.
29
+
1. Click **Save**.<br/><img src={useBaseUrl('img/security/provision-onelogin-rename-app.png')} alt="Display name of the app" style={{border: '1px solid gray'}} width="700" />
30
+
31
+
### Step 2: Set up single sign-on
32
+
33
+
Follow the directions in [Configure a SAML app in OneLogin](/docs/manage/security/saml/integrate-onelogin/#configure-a-saml-app-in-onelogin) beginning with the step where you configure the **SSO** tab.<br/><img src={useBaseUrl('img/security/provision-onelogin-sso-tab.png')} alt="SSO tab" style={{border: '1px solid gray'}} width="700" />
34
+
35
+
:::note
36
+
On the **Configuration** tab, for **SCIM Base URL** enter the [API endpoint for your deployment](/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security) for the SCIM API using the format `<api-endpoint>/v1/scim/`. For example, `https://api.sumologic.com/api/v1/scim`. You will perform additional configuration of the app later.
37
+
:::
38
+
39
+
### Step 3: Set up roles
40
+
41
+
1. Add a custom role field:
42
+
1. From the main menu, select **Users > Custom User Fields**.
1. Select the application you created in Step 1.<br/><img src={useBaseUrl('img/security/provision-onelogin-app.png')} alt="New app" style={{border: '1px solid gray'}} width="700" />
1. Add the rest of the parameters as shown:<br/><img src={useBaseUrl('img/security/provision-onelogin-all-parameters.png')} alt="All parameters" style={{border: '1px solid gray'}} width="700" />
58
+
59
+
### Step 4: Set up provisioning
60
+
61
+
1. In the app, select **Configuration**.
62
+
1. Configure the app:
63
+
1. Enter the **SAML Audience URL** (entity ID) and **SAML Consumer URL** (assertion consumer URL) for your Sumo Logic instance:<br/><img src={useBaseUrl('img/security/provision-onelogin-configuration.png')} alt="Configuration for the app" style={{border: '1px solid gray'}} width="700" /><br/>Obtain the assertion consumer URL and entity ID from the SAML configuration of the Sumo Logic tenant where you will provision users. You set up this [SAML configuration](/docs/manage/security/saml/integrate-onelogin/#configure-saml-in-sumo) in Step 2.<br/><img src={useBaseUrl('img/security/provision-onelogin-sumologic-saml-settings.png')} alt="ACS and entity ID from Sumo Logic" style={{border: '1px solid gray'}} width="800" />
64
+
1. For **API Status**, click **Enable**.
65
+
1. For **SCIM Base URL**, ensure that you have entered the [API endpoint for your deployment](/docs/api/getting-started/#sumo-logic-endpoints-by-deployment-and-firewall-security) for the SCIM API using the format `<api-endpoint>/v1/scim/`. For example, `https://api.sumologic.com/api/v1/scim`.
66
+
1. For **SCIM JSON Template**, enter the following:
67
+
```json
68
+
{
69
+
"schemas": [
70
+
"urn:ietf:params:scim:schemas:core:2.0:User"
71
+
],
72
+
"userName": "{$parameters.scimusername}",
73
+
"name": {
74
+
"familyName": "{$user.lastname}",
75
+
"givenName": "{$user.firstname}"
76
+
},
77
+
"emails": [{
78
+
"value": "{$user.email}",
79
+
"type": "work",
80
+
"primary": true
81
+
}],
82
+
"roles": [{
83
+
"value": "{$user.custom_fields.roles}",
84
+
"primary": true
85
+
}]
86
+
}
87
+
```
88
+
1. For **Custom Headers**, enter:
89
+
```
90
+
Accept: application/scim+json
91
+
Content-Type: application/scim+json
92
+
```
93
+
1. For **SCIM Bearer Token**, use [Base64 encoding](https://www.base64encode.org/) to encode `<access ID>:<access key>` (see [Prerequisites](#prerequisites)). Enter the resulting value into the **SCIM Bearer Token** field.
1. From the main menu, select **Applications > Applications**.
116
+
1. Select the application you created in Step 1.
117
+
1. Select **Users**.
118
+
1. Click **Pending** on the user you want to approve for provisioning.<br/><img src={useBaseUrl('img/security/provision-onelogin-approve-user.png')} alt="Pending user" style={{border: '1px solid gray'}} width="800" />
When you modify the name, email, or role of a user assigned the app in OneLogin, the changes will be synced to the corresponding user in Sumo Logic.
125
+
126
+
If you unassign a user from the app in OneLogin, the corresponding user is deactivated in Sumo Logic. (If you later try to reassign that same user to the app, it will result in an error in Sumo Logic. You must delete the old user from Sumo Logic first so that the user can be provisioned once again from OneLogin.)
0 commit comments