95 - Need error message if user does not have correct roles

[nlaprell]

• Updated login messaging when no queries have been created:
  • Messaging appears in a yellow "warning" alert box.
  • The wizard user is directed to the crud page (with a hyperlink) to create queries.
  • The search user is still directed to have a wizard user create queries.
• The search button on the navigation is now hidden if there are no queries to search.
  • The search button appears as soon as a query is created.
• The wizard user now has a data-explorer-search-role as well (fixed search errors for the wizard user)
• Crud get requests now require the data-explorer-search-role instead of the data-explorer-wizard-role since they are used for searching.

[cskeefer]

All the updated messages and hiding the search menu look good. I feel like the changes to the following files to check for is-search-user rather than is-wizard-user would allow a search user to call the end points (by pasting in the URL in the browser). Since those are used Edit config menu, should we be checking for is-wizard-user instead?

• src/main/ml-modules/root/server/endpoints/api-crud-get-query-view.xqy
• src/main/ml-modules/root/server/endpoints/api-crud-list-queries.xqy
• src/main/ml-modules/root/server/endpoints/api-crud-list-views.xqy

[nlaprell]

@cskeefer - Those three endpoints are actually GET endpoints and do not perform any CRUD operations. The search page uses them when selecting a database, query, and view to search, so if we validate against the wizard role, it breaks for the search user when searching.

In testing, I manually pasted in the crud page into the browser, and while it does display the interface, any CRUD operation on that page immediately throws a 401 as expected and no data is changed. Eventually, we should probably throw an error on the page and disable the forms, but it works as is right now.

[cskeefer]

@nlaprell got it, sounds good!