Merge branch 'main' into main

README.md

@@ -93,7 +93,7 @@ Subsequent executions will check for updated dependencies, if there are none, it
 
 License
 =======
-Copyright (c) 2014-2025 [SUSE, LLC.](https://www.suse.com/)
+Copyright (c) 2014-2026 [SUSE, LLC.](https://www.suse.com/)
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.

docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-generic-oidc.md

@@ -35,6 +35,12 @@ In your IdP, create a new client with the settings below:
 
 In the new OIDC client, create mappers to expose the user's fields.
 
+:::note
+
+The `groups` and `full_group_path` claims generated by the Groups and Group Path mappers, which you create within the OIDC client in your Identity Provider, should be JSON arrays, e.g. `"groups":["admins","devs","qa"]` and `"full_group_path":["/admins","/devs","/qa"]`.
+
+:::
+
   1. Create a new `Groups Mapper` with the settings below:
 
     Setting | Value
@@ -153,4 +159,4 @@ In some cases, the "Invalid grant_type" error message may be misleading and is a
 
 ## Configuring OIDC Single Logout (SLO)
 
-<ConfigureSLOOidc />
+<ConfigureSLOOidc />

versioned_docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-generic-oidc.md

@@ -29,7 +29,14 @@ Consult the documentation for your specific IdP to complete the listed prerequis
     `Access Type` | `confidential`
     `Valid Redirect URI` | `https://yourRancherHostURL/verify-auth`
 
-  - In the new OIDC client, create mappers to expose the users fields.
+  - In the new OIDC client, create mappers to expose the user's fields.
+
+    :::note
+
+    The `groups` and `full_group_path` claims generated by the Groups and Group Path mappers, which you create within the OIDC client in your Identity Provider, should be JSON arrays, e.g. `"groups":["admins","devs","qa"]` and `"full_group_path":["/admins","/devs","/qa"]`.
+
+    :::
+
     - Create a new Groups Mapper with the settings below:
 
       Setting | Value

versioned_docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-generic-oidc.md

@@ -29,7 +29,14 @@ Consult the documentation for your specific IdP to complete the listed prerequis
     `Access Type` | `confidential`
     `Valid Redirect URI` | `https://yourRancherHostURL/verify-auth`
 
-  - In the new OIDC client, create mappers to expose the users fields.
+  - In the new OIDC client, create mappers to expose the user's fields.
+
+    :::note
+
+    The `groups` and `full_group_path` claims generated by the Groups and Group Path mappers, which you create within the OIDC client in your Identity Provider, should be JSON arrays, e.g. `"groups":["admins","devs","qa"]` and `"full_group_path":["/admins","/devs","/qa"]`.
+
+    :::
+
     - Create a new Groups Mapper with the settings below:
 
       Setting | Value

versioned_docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-generic-oidc.md

@@ -29,7 +29,14 @@ Consult the documentation for your specific IdP to complete the listed prerequis
     `Access Type` | `confidential`
     `Valid Redirect URI` | `https://yourRancherHostURL/verify-auth`
 
-  - In the new OIDC client, create mappers to expose the users fields.
+  - In the new OIDC client, create mappers to expose the user's fields.
+
+    :::note
+
+    The `groups` and `full_group_path` claims generated by the Groups and Group Path mappers, which you create within the OIDC client in your Identity Provider, should be JSON arrays, e.g. `"groups":["admins","devs","qa"]` and `"full_group_path":["/admins","/devs","/qa"]`.
+
+    :::
+
     - Create a new Groups Mapper with the settings below:
 
       Setting | Value

versioned_docs/version-2.13/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-generic-oidc.md

@@ -35,6 +35,12 @@ In your IdP, create a new client with the settings below:
 
 In the new OIDC client, create mappers to expose the user's fields.
 
+:::note
+
+The `groups` and `full_group_path` claims generated by the Groups and Group Path mappers, which you create within the OIDC client in your Identity Provider, should be JSON arrays, e.g. `"groups":["admins","devs","qa"]` and `"full_group_path":["/admins","/devs","/qa"]`.
+
+:::
+
   1. Create a new `Groups Mapper` with the settings below:
 
     Setting | Value

versioned_docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-generic-oidc.md

@@ -29,7 +29,14 @@ Consult the documentation for your specific IdP to complete the listed prerequis
     `Access Type` | `confidential`
     `Valid Redirect URI` | `https://yourRancherHostURL/verify-auth`
 
-  - In the new OIDC client, create mappers to expose the users fields.
+  - In the new OIDC client, create mappers to expose the user's fields.
+
+    :::note
+
+    The `groups` and `full_group_path` claims generated by the Groups and Group Path mappers, which you create within the OIDC client in your Identity Provider, should be JSON arrays, e.g. `"groups":["admins","devs","qa"]` and `"full_group_path":["/admins","/devs","/qa"]`.
+
+    :::
+
     - Create a new Groups Mapper with the settings below:
 
       Setting | Value