RLS do not show all roles in dropdown

[ziggekatten]

We have 120+ roles, and quite a lot of RLS rules for shared data. Adding new roles is no problem, but suddenly no newly created roles shows up in the Row Level Security form Roles dropdown. Typing its name does not making it showup. Is there some limit set here that I'm not aware of?

[dosubot[bot]]

The issue you're experiencing with newly created roles not appearing in the Row Level Security (RLS) form's Roles dropdown might be related to the mechanism used to fetch and display roles. The roles are fetched using an AsyncSelect component, which makes an API call to the endpoint /api/v1/rowlevelsecurity/related/roles. This endpoint uses query parameters for filtering, pagination, and page size ^[1].

If the roles are not appearing, consider checking the following:

1. API Response: Ensure that the API call to /api/v1/rowlevelsecurity/related/roles is returning the expected results. You can do this by inspecting the network requests in your browser's developer tools.

2. Pagination and Page Size: If there are many roles, pagination might be affecting the visibility of newly created roles. Check if the page size is set appropriately to display all roles.

3. Caching: There might be caching issues affecting the visibility of new roles. Try clearing any caches or refreshing the page to see if the roles appear.

4. Role Filtering: Ensure that the filtering criteria in the dropdown are not excluding the new roles. Double-check the search input and any filters applied.

If these steps do not resolve the issue, it might be necessary to investigate further into the backend logic or configuration settings that could affect role visibility.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[dosubot[bot]]

To adjust the number of roles returned in the list, you need to modify the page_size parameter in the API request to /api/v1/rowlevelsecurity/related/roles. The loadRoleOptions function in the Superset frontend code is responsible for this request, and it includes a page_size parameter that you can change. Here's how it's set in the code:

const loadRoleOptions = useMemo(
  () =>
    (input = '', page: number, pageSize: number) => {
      const query = rison.encode({
        filter: input,
        page,
        page_size: pageSize, // This is where the page size is set
      });
      return SupersetClient.get({
        endpoint: `/api/v1/rowlevelsecurity/related/roles?q=${query}`,
      }).then(response => {
        const list = response.json.result.map(
          (item: { value: number; text: string }) => ({
            label: item.text,
            value: item.value,
          }),
        );
        return { data: list, totalCount: response.json.count };
      });
    },
  [],
);

To increase the number of roles returned, you can increase the pageSize argument when calling loadRoleOptions ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[ziggekatten]

@dosu, setting the page_size parameter above 100 only returns 100 roles: /api/v1/rowlevelsecurity/related/roles?q={"page_size":1000}

It seems that somewhere there is an cap of 100

[dosubot[bot]]

The limit of 100 roles might be enforced on the server side, possibly as a default pagination limit for API responses. While I couldn't find specific documentation or code references in the Superset repository that explicitly mention a 100 roles limit, you can try checking the server-side configuration or code that handles pagination for this endpoint.

One approach is to look into the backend code where the API endpoint /api/v1/rowlevelsecurity/related/roles is implemented. There might be a hardcoded limit or a configuration setting that enforces this cap. Additionally, you can explore the superset_config.py file to see if there are any relevant settings that might be affecting this limit.

If you have access to the backend code, you might want to search for any pagination logic or constants that could be setting this limit. If you find a specific setting or code section, you can adjust it to allow more roles to be returned.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[ziggekatten]

Closing this and added an issue instead