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
### Assigning a Role from Keycloak to Shuffle for a New User
186
+
187
+
If you want to assign a Shuffle organization role (`admin`, `user`, `org-reader`) from your Keycloak client, you can achieve this using the following method:
188
+
189
+
Steps to Assign Roles
190
+
191
+
1. In your Keycloak client, create three new roles with the names `shuffle-admin`, `shuffle-user`, and `shuffle-org-reader`, as shown in the image below:
2. After creating the roles, assign them to the users you want. The `shuffle-admin`, `shuffle-user`, and `shuffle-org-reader` roles in Keycloak correspond to the `admin`, `user`, and `org-reader` roles in Shuffle.
196
+
197
+
3. Once the roles are assigned to users, navigate to:
- After completing these settings, all newly created users will be assigned roles based on their Keycloak roles. If no role is assigned, the default role will be `user`.
211
+
- As of now, role assignment is only applied to newly generated users. If a user already exists in Shuffle, changing their role in Keycloak will **not** update their role in Shuffle.
212
+
In this case, you can manually change the user's role from the `https://shuffler.io/admin?tab=users` page.
213
+
- You can achieve this behavior starting from Shuffle version 2.0.1 or later. Make sure you are using this version or a newer one
214
+
215
+
216
+
185
217
### Azure AD
186
218
To use OpenID with Azure AD, Shuffle supports OpenID connect with the use of Client IDs and Client secrets. To set up OpenID Connect with Azure, we use "ID_token" authentication. This entails a few normal steps regarding app creation in Azure App Registration.
**Note**: Ensure that the "email" field is included in the SSO response from your SSO provider. If this field is empty, you may encounter errors. The email from your SSO provider will be assigned as the username in Shuffle.
229
261
262
+
263
+
264
+
### How to Assign a Role to a New User from an SSO Provider (OpenID Connect) in Shuffle
265
+
266
+
If you want to assign a role to a user from an SSO provider, you can do so using the following method:
267
+
268
+
1. Create three roles in your SSO application/client:
269
+
-`shuffle-admin`
270
+
-`shuffle-user`
271
+
-`shuffle-org-reader`
272
+
273
+
2. Assign one of these roles to new users when granting them access to the application/client.
274
+
- The `shuffle-admin`, `shuffle-user`, and `shuffle-org-reader` roles in your SSO provider correspond to the `admin`, `user`, and `org-reader` roles in Shuffle.
275
+
276
+
3. Ensure that the `roles` claim is included in the **ID token** response from your SSO provider.
277
+
278
+
After completing these steps, all newly created users will be assigned roles in Shuffle based on their assigned role in the SSO provider.
279
+
280
+
- If none of the specified roles are assigned, or if the `roles` claim is missing, the user will be assigned the default role: **`user`** in Shuffle.
281
+
282
+
Important Notes
283
+
284
+
1. Currently, this feature is only available for **OpenID Connect**. Support for **SAML SSO** may be added in the future.
285
+
2. At this time, role assignments only apply to newly created users. If a user already exists in Shuffle, changing their role in the SSO provider **will not** update their role in Shuffle.
286
+
- To manually update an existing user’s role in Shuffle, please visit the **Shuffle Admin Page**:
3. You can achieve this behavior starting from Shuffle version 2.0.1 or later. Make sure you are using this version or a newer one.
289
+
290
+
If you have any questions or need further assistance, please feel free to reach out to us at **[[email protected]](mailto:[email protected])**.
291
+
292
+
230
293
## Detection Manager
231
294
The Shuffle Detection Manager is a system introduced in beta in December 2024, allowing Shuffle to work with platforms like Tenzir and other systems to help with Detection Engineering. The goal of the system is not to replace actual detection systems themselves, but to offer a centralized way to control Detection rules across tenants and different tools. As an example, **below is a focus on Sigma rules with Tenzir**. The system is tested with Yara rules, Email detection rules and custom rule systems.
0 commit comments