After selecting App Search, I can no longer select Workplace Search

Elastic Search
1

When I logged into Enterprise Search via my AD/ES-Native user, I was given the option to choose either App Search or Workplace Search. I selected App Search. Now, when I go back to /ent/select, Workplace Search no longer shows up as an option.

If I hit /ws, I get redirected to /as.

If I log in via the elastic super user, I can switch just fine.

I have a trial going on my Elasticsearch cluster, so I should have access to all features. So lack of a license shouldn't be the problem.

Would the fact I don't have any WS sources configured yet have something to do with it?

Any other ideas?

Edit:
This is all on version 7.12.

I have enterprise search configured to use elasticsearch-native for auth, and ES is configured to use AD.

2

Heya David!

Let's get this sorted out together. It appears that role mappings are at play here. Did you manually apply role mappings in the App Search interfaces for the AD-Native user using the superadmin? Perhaps even via the Workplace Search Role Mappings UI?

3

Nope. I just double checked. There's a nice big "No Role Mappings yet" message on the App Search Users & Roles screen.

I'm using the Elasticsearch Ansible role to manage roles via the file based system. The user in question is mapped to the "users" role via an AD group.

4

And using the superuser, can you confirm that no role mapping exist in the Workplace Search Role Mappings UI please?

1 Like
5

Screenshot_2021-04-20 Elastic Workplace Search
Screenshot_2021-04-20 Elastic Workplace Search957×285 17.4 KB

That is what I have set for Workplace search.

6

FYI, I deleted the two email mappings, then added one based on an ES Native role. That let my normal user start switching between the two tools.

7

Awesome - glad you managed to narrow it down - role mappings can be tricky at times. Another thing to keep in mind is if you want to make sure end-users do not have access to one of the two products, you must create at least one role mapping in the product to be restricted (in general, declaratively mapping the superuser to an admin role will do).