Introduce role description field #107088

slobodanadamovic · 2024-04-04T09:58:27Z

This PR introduces new description field to roles definitions.

Role API:

POST /_security/role/viewer
{
  "description": "Grants permission to view all indices.",
  "indices": [
    {
      "names": [ "*" ],
      "privileges": [ "read" , "view_index_metadata"]
    }
  ]
}

File-based role:

viewer:
  description: 'Grants permission to view all indices.' 
  indices:
    - names: [ '*' ]
      privileges: [ 'read', 'view_index_metadata' ]

Note: I will address the doc changes in a followup PR.

elasticsearchmachine · 2024-04-04T10:00:31Z

Hi @slobodanadamovic, I've created a changelog YAML for you.

…/elasticsearch into sa-add-role-description

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

…ole-description

The method for `RoleDescriptor` parsing is becoming more complex due to its usage being shared between API keys, file-based and native roles. In some cases we allow 2.X format, in others we disallow restrictions. Having a single method with multiple boolean flags that control inclusion/exclusion of fields is becoming hard to extend. This refactoring aims to allow easier introduction of new fields that should be conditionally supported in some cases but not others. One of such cases is introduction of `description` field that should only be supported for file-based and native roles but not for roles embedded in API keys.

…tor-role-parsing # Conflicts: # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authz/store/FileRolesStore.java

…c/elasticsearch into sa-add-role-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/action/role/PutRoleRequestBuilder.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authc/CrossClusterAccessSubjectInfo.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptor.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptorsIntersection.java # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptorTests.java # x-pack/plugin/security/src/internalClusterTest/java/org/elasticsearch/xpack/security/authc/ApiKeyIntegTests.java # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authz/store/FileRolesStore.java # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authz/store/NativeRolesStore.java # x-pack/plugin/security/src/test/java/org/elasticsearch/test/TestSecurityClient.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authc/ApiKeyServiceTests.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authz/permission/FieldPermissionsTests.java

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

The method for `RoleDescriptor` parsing is becoming more complex due to its usage being shared between API keys, file-based and native roles. In some cases we allow 2.X format, in others we disallow restrictions. Having a single method with multiple boolean flags that control inclusion/exclusion of fields is becoming hard to extend. This refactoring aims to allow easier introduction of new fields that should be conditionally supported in some cases but not others. One of such cases is introduction of `description` field that should only be supported for file-based and native roles but not for roles embedded in API keys. Relates to: #107088

…ole-description # Conflicts: # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/action/apikey/ApiKey.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/action/apikey/BulkUpdateApiKeyRequestTranslator.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/action/apikey/CreateApiKeyRequestBuilder.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/action/apikey/UpdateApiKeyRequestTranslator.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/action/role/PutRoleRequestBuilder.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authc/CrossClusterAccessSubjectInfo.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptor.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptorsIntersection.java # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/action/service/GetServiceAccountResponseTests.java # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptorTests.java # x-pack/plugin/security/qa/security-trial/src/javaRestTest/java/org/elasticsearch/xpack/security/role/RoleWithRemoteIndicesPrivilegesRestIT.java # x-pack/plugin/security/src/internalClusterTest/java/org/elasticsearch/xpack/security/authc/ApiKeyIntegTests.java # x-pack/plugin/security/src/internalClusterTest/java/org/elasticsearch/xpack/security/authc/apikey/ApiKeySingleNodeTests.java # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authc/ApiKeyService.java # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authz/store/FileRolesStore.java # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authz/store/NativeRolesStore.java # x-pack/plugin/security/src/test/java/org/elasticsearch/test/TestSecurityClient.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authc/ApiKeyServiceTests.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authz/permission/FieldPermissionsTests.java

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

…ole-description

## Summary In preparation for the KB UI and ES API to accept `description` for Roles, Kibana `get`, `getAll`, and `put` Roles routes should handle a description. ## Testing Start KB/ES locally In Dev Tools PUT role: ``` PUT kbn:api/security/role/mytestrole { "description": "This is a test role", "metadata": { "version": 1 }, "elasticsearch": { "cluster": [ ], "indices": [ ] }, "kibana": [ { "base": [ ], "feature": { "discover": [ "all" ], "visualize": [ "all" ], "dashboard": [ "all" ], "dev_tools": [ "read" ], "advancedSettings": [ "read" ], "indexPatterns": [ "read" ], "graph": [ "all" ], "apm": [ "read" ], "maps": [ "read" ], "canvas": [ "read" ], "infrastructure": [ "all" ], "logs": [ "all" ], "uptime": [ "all" ] }, "spaces": [ "*" ] } ] } ``` This will fail since ES doesn't accept `descriptions` yet Pull the ES Role Description PR elastic/elasticsearch#107088 and run `yarn es source` and `yarn start` Rerun the PUT above, receive 204! Check the role `description` with a GET: ``` GET kbn:api/security/role/mytestrole ``` <img width="1712" alt="Screenshot 2024-04-30 at 9 43 32 PM" src="https://github.com/elastic/kibana/assets/21210601/20394086-f223-4be8-8660-eb8d3930116c"> It has a limit of 2048 per the requirements: <img width="2248" alt="Screenshot 2024-04-30 at 9 45 13 PM" src="https://github.com/elastic/kibana/assets/21210601/7dc97a8e-1246-49e4-954e-885be433c7c7">

jakelandis

Changes are looking good. A few comments.

(also, this really highlights that we should refactor some of this ... changing 55 files with over 1k lines of change to add a description field is a bit excessive, but nice job finding all the places).

jakelandis · 2024-05-01T21:08:44Z

...in/security/src/main/java/org/elasticsearch/xpack/security/authz/store/NativeRolesStore.java

+                    listener.onFailure(
+                        new IllegalStateException(
+                            "all nodes must have transport version ["
+                                + TransportVersions.SECURITY_ROLE_DESCRIPTION


the error message pattern been updated to not include "transport" in message and use .toReleaseVersion()

Good catch! Will fix.

Fixed in: 35a80dc

...ck/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptor.java

jakelandis · 2024-05-01T21:35:26Z

...g/elasticsearch/xpack/security/crossclusteraccess/CrossClusterAccessHeadersForCcsRestIT.java

@@ -193,6 +194,7 @@ public void testCrossClusterAccessHeadersSentSingleRemote() throws Exception {
                        null,
                        null,
                        null,
+                        null,


nit: can you add a comment here that description is intentinally null and never sent across clusters (wouldn't hurt to make a similar comment in org.elasticsearch.xpack.core.security.authz.permission.SimpleRole#getRoleDescriptorsIntersectionForRemoteCluster )

jakelandis · 2024-05-01T21:44:25Z

...ity/src/test/java/org/elasticsearch/xpack/security/authz/store/CompositeRolesStoreTests.java

@@ -964,7 +964,8 @@ public ClusterPermission.Builder buildPermission(ClusterPermission.Builder build
            new RoleDescriptor.RemoteIndicesPrivileges[] {
                RoleDescriptor.RemoteIndicesPrivileges.builder("remote-*", "remote").indices("abc-*", "xyz-*").privileges("read").build(),
                RoleDescriptor.RemoteIndicesPrivileges.builder("remote-*").indices("remote-idx-1-*").privileges("read").build(), },
-            null
+            null,


IIUC, since we don't move the description from role descriptors to roles via the composite role store, the description will never get cached in the role cache. I think that is correct to save memory, but could be problematic if we ever pull from the cache in any CRUD workflows. Is it possible to add a test that it is not part of the cache + a comment that we are explicilty not caching the description ?

That's correct. Thanks for calling it out. From my point of view, the description is only relevant for representation and it's not relevant when constructing internal role models for checking permissions (same as metadata).

could be problematic if we ever pull from the cache in any CRUD workflows. Is it possible to add a test that it is not part of the cache + a comment that we are explicitly not caching the description ?

Makes sense to add a comment but not sure how I would test this. A single role can be built from multiple role descriptors. What we cache is a Role data model which per contract does not define a description property.

jakelandis · 2024-05-01T21:53:16Z

...n/security/src/main/java/org/elasticsearch/xpack/security/support/SecuritySystemIndices.java

            .setSettings(getMainIndexSettings())
            .setAliasName(SECURITY_MAIN_ALIAS)
            .setIndexFormat(INTERNAL_MAIN_INDEX_FORMAT)
            .setVersionMetaKey(SECURITY_VERSION_STRING)
            .setOrigin(SECURITY_ORIGIN)
            .setThreadPools(ExecutorNames.CRITICAL_SYSTEM_INDEX_THREAD_POOLS)
+            .setPriorSystemIndexDescriptors(
+                List.of(
+                    SystemIndexDescriptor.builder()


nit: can you DRY up this builder and only diverge as needed.

Addressed in be602ab

I've also put the remote_cluster under the same new mapping version: 981bec3

jakelandis · 2024-05-01T21:55:46Z

...n/security/src/main/java/org/elasticsearch/xpack/security/support/SecuritySystemIndices.java

@@ -385,6 +402,12 @@ private XContentBuilder getMainIndexMappings() {
                    builder.field("type", "keyword");
                    builder.endObject();

+                    if (version >= SecurityMainIndexMappingVersion.ADD_DESCRIPTION_FIELD) {


why do we need this conditional ? don't we always want to install the mappings on newer versions ?

The getMainIndexMappings method now accepts version and it is also called with the lower mapping version (1) when creating descriptor of prior versions.

If you want to, you could make use of VersionId interface to provide a slightly nicer interface to SecurityMainIndexMappingVersion

TIL Implementing VersionId would fit perfectly here. Thanks for the suggestion.

jakelandis · 2024-05-01T22:00:03Z

...n/security/src/main/java/org/elasticsearch/xpack/security/support/SecuritySystemIndices.java

            .setSettings(getMainIndexSettings())
            .setAliasName(SECURITY_MAIN_ALIAS)
            .setIndexFormat(INTERNAL_MAIN_INDEX_FORMAT)
            .setVersionMetaKey(SECURITY_VERSION_STRING)
            .setOrigin(SECURITY_ORIGIN)
            .setThreadPools(ExecutorNames.CRITICAL_SYSTEM_INDEX_THREAD_POOLS)
+            .setPriorSystemIndexDescriptors(


Can someone help to understand why we need to provide the prior index descriptors ? Shouldn't the logic always be install the new version as soon as possible (at least for passive changes such additions) ?

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/action/role/PutRoleRequest.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptor.java # x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/store/ReservedRolesStore.java # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/action/apikey/BulkUpdateApiKeyRequestTests.java # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/action/apikey/CreateApiKeyRequestTests.java # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/action/apikey/UpdateApiKeyRequestTests.java # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptorTests.java # x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/authz/permission/SimpleRoleTests.java # x-pack/plugin/security/qa/security-trial/src/javaRestTest/java/org/elasticsearch/xpack/security/apikey/ApiKeyRestIT.java # x-pack/plugin/security/qa/security-trial/src/javaRestTest/java/org/elasticsearch/xpack/security/crossclusteraccess/CrossClusterAccessHeadersForCcsRestIT.java # x-pack/plugin/security/src/internalClusterTest/java/org/elasticsearch/xpack/security/authc/ApiKeyIntegTests.java # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authc/ApiKeyService.java # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authz/store/NativeRolesStore.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authc/ApiKeyServiceTests.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authz/AuthorizationServiceIntegTests.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authz/RBACEngineTests.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authz/store/CompositeRolesStoreTests.java # x-pack/plugin/security/src/test/java/org/elasticsearch/xpack/security/authz/store/NativeRolesStoreTests.java # x-pack/plugin/security/src/test/resources/org/elasticsearch/xpack/security/authz/store/roles.yml # x-pack/qa/rolling-upgrade/src/test/java/org/elasticsearch/upgrades/ApiKeyBackwardsCompatibilityIT.java

slobodanadamovic · 2024-05-07T12:19:13Z

...ugin/core/src/test/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptorTests.java

-
-        RemoteClusterPermissions remoteClusters = RemoteClusterPermissions.NONE;
-        if (allowRemoteClusters && randomBoolean()) {
-            randomRemoteClusterPermissions(randomIntBetween(1, 5));


While refactoring random role descriptor creation, I've noticed that we've never assigned randomRemoteClusterPermissions to remoteClusters. This uncovered two failing tests. It is fixed in RoleDescriptorTestHelper.

whoops ! thanks for fixing.

jakelandis

LGTM

jakelandis · 2024-05-07T17:41:07Z

...ck/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptor.java

@@ -187,6 +193,7 @@ public RoleDescriptor(
            ? remoteClusterPermissions
            : RemoteClusterPermissions.NONE;
        this.restriction = restriction != null ? restriction : Restriction.NONE;
+        this.description = description;


nit: I have slight preference to check for null and if null then set to empty string. It can eliminate a class of problems and things to check and better matches the other @ Nullable -> non-null class members.

I was undecided here and went with null. Agreed, using empty string is more consistent and simplifies the checks. I will change this.

jakelandis · 2024-05-07T17:54:13Z

...in/security/src/main/java/org/elasticsearch/xpack/security/authz/store/NativeRolesStore.java

+                    && clusterService.state().getMinTransportVersion().before(TransportVersions.SECURITY_ROLE_DESCRIPTION)) {
+                        listener.onFailure(
+                            new IllegalStateException(
+                                "all nodes must have transport version ["


nit: all nodes must have version ["

jakelandis · 2024-05-07T18:04:22Z

...n/security/src/main/java/org/elasticsearch/xpack/security/support/SecuritySystemIndices.java

-                    {
-                        builder.field("type", "object");
-                        builder.startObject("properties");
+                    if (mappingVersion.onOrAfter(SecurityMainIndexMappingVersion.ADD_REMOTE_CLUSTER_AND_DESCRIPTION_FIELDS)) {


thank you for handling this !

jakelandis · 2024-05-07T18:27:42Z

...ugin/core/src/test/java/org/elasticsearch/xpack/core/security/authz/RoleDescriptorTests.java

-
-        RemoteClusterPermissions remoteClusters = RemoteClusterPermissions.NONE;
-        if (allowRemoteClusters && randomBoolean()) {
-            randomRemoteClusterPermissions(randomIntBetween(1, 5));


whoops ! thanks for fixing.

jakelandis · 2024-05-07T18:44:48Z

.../rolling-upgrade/src/test/java/org/elasticsearch/upgrades/RolesBackwardsCompatibilityIT.java

+import static org.hamcrest.Matchers.equalTo;
+import static org.hamcrest.Matchers.notNullValue;
+
+public class RolesBackwardsCompatibilityIT extends AbstractUpgradeTestCase {


I appreciate the effort but writing and running BWC tests for every change to our wire serialization is cost prohibitive (both in terms of developer time and CPU time). For normal additions like this it is not needed. However, I would suggest to leave this as it provides a nice framework for future changes we might want to explicitly test. (IMO, the things we want to test are generally breaking changes or major changes to how things work internally or any migrations triggered on upgrades )

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

…ole-description

This commit updates Role API docs to include new description field (introduced in #107088) and adds descriptions for all built-in roles.

Introduce role description field

248c615

slobodanadamovic added :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC Team:Security Meta label for security team test-full-bwc Trigger full BWC version matrix tests labels Apr 4, 2024

slobodanadamovic self-assigned this Apr 4, 2024

elasticsearchmachine added the v8.14.0 label Apr 4, 2024

slobodanadamovic added the >enhancement label Apr 4, 2024

Update docs/changelog/107088.yaml

9b540d0

slobodanadamovic added 9 commits April 4, 2024 12:50

Fix serialization issue

42dbaab

Merge branch 'sa-add-role-description' of github.com:slobodanadamovic…

ad6e48f

…/elasticsearch into sa-add-role-description

Fix failing bwc test

fca71bb

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

906d537

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

ca60fb3

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

Refactor role descriptor parsing

b22fe9a

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

546602f

…ole-description

Fix failing tests (API key roles do not support description field)

23d3396

slobodanadamovic mentioned this pull request Apr 12, 2024

Refactor role descriptor parsing #107430

Merged

slobodanadamovic added 3 commits April 15, 2024 09:54

Merge branch 'main' of github.com:elastic/elasticsearch into sa-refac…

621959b

…tor-role-parsing # Conflicts: # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authz/store/FileRolesStore.java

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

ce3baab

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

slobodanadamovic added 7 commits April 17, 2024 10:21

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

b2a9d7d

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

Fix failing API key tests

48b069f

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

c3ed4ba

…ole-description

Fix another failing test

9dbcfaa

spotless

e74a90d

Relax cross cluster role parsing - we have checks in place

8da5db4

Fix failing tests

05aa831

kc13greiner mentioned this pull request May 1, 2024

Adding optional Description field to Roles APIs elastic/kibana#182039

Merged

jakelandis reviewed May 1, 2024

View reviewed changes

slobodanadamovic added 9 commits May 6, 2024 12:41

TransportVersions.SECURITY_ROLE_DESCRIPTION.toReleaseVersion

35a80dc

nit: comment why description is never send across clusters

1fb938a

Implement VersionId and dry up getSecurityMainIndexDescriptor

be602ab

remove comment

491b410

Remove unnecessary INTERNAL_MAIN_INDEX_MAPPINGS_FORMAT constant

52fd232

Update security index mapping version to include remote_cluster

981bec3

Fix issue with overloaded createRole method

e20ca64

Fix failing test

5ceb492

slobodanadamovic commented May 7, 2024

View reviewed changes

Another test fix

981b203

slobodanadamovic requested a review from jakelandis May 7, 2024 13:22

jakelandis approved these changes May 7, 2024

View reviewed changes

slobodanadamovic added 6 commits May 7, 2024 21:39

remove "transport" from exception message

4507041

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

e768c8b

…ole-description # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java

null -> empty string

0c56fef

Fix toString test

990d9c3

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

91ccbfb

…ole-description

Merge branch 'main' of github.com:elastic/elasticsearch into sa-add-r…

6a5c379

…ole-description

slobodanadamovic removed the test-full-bwc Trigger full BWC version matrix tests label May 8, 2024

slobodanadamovic merged commit 7b62ea9 into elastic:main May 8, 2024
20 checks passed

legrego mentioned this pull request May 8, 2024

Allow roles to have an optional description elastic/kibana#173570

Closed

slobodanadamovic mentioned this pull request May 10, 2024

[docs] Document new role description field #108422

Merged

slobodanadamovic added a commit that referenced this pull request May 14, 2024

[docs] Document new role description field (#108422)

77ce605

This commit updates Role API docs to include new description field (introduced in #107088) and adds descriptions for all built-in roles.

albertzaharovits mentioned this pull request Jul 4, 2024

Spec for the new Query Role API elastic/elasticsearch-specification#2676

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Introduce role description field #107088

Introduce role description field #107088

slobodanadamovic commented Apr 4, 2024 •

edited

Loading

elasticsearchmachine commented Apr 4, 2024

jakelandis left a comment

jakelandis May 1, 2024

slobodanadamovic May 3, 2024

slobodanadamovic May 7, 2024

jakelandis May 1, 2024

jakelandis May 1, 2024

slobodanadamovic May 3, 2024

jakelandis May 1, 2024

slobodanadamovic May 7, 2024

slobodanadamovic May 7, 2024

jakelandis May 1, 2024

slobodanadamovic May 3, 2024

thecoop May 3, 2024

slobodanadamovic May 3, 2024 •

edited

Loading

jakelandis May 1, 2024

slobodanadamovic May 7, 2024 •

edited

Loading

jakelandis May 7, 2024

jakelandis left a comment

jakelandis May 7, 2024

slobodanadamovic May 7, 2024 •

edited

Loading

jakelandis May 7, 2024

jakelandis May 7, 2024

jakelandis May 7, 2024

jakelandis May 7, 2024

Introduce role description field #107088

Introduce role description field #107088

Conversation

slobodanadamovic commented Apr 4, 2024 • edited Loading

elasticsearchmachine commented Apr 4, 2024

jakelandis left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

slobodanadamovic May 3, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

slobodanadamovic May 7, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jakelandis left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

slobodanadamovic May 7, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

slobodanadamovic commented Apr 4, 2024 •

edited

Loading

slobodanadamovic May 3, 2024 •

edited

Loading

slobodanadamovic May 7, 2024 •

edited

Loading

slobodanadamovic May 7, 2024 •

edited

Loading