When we see this error in SearchStax Managed Search service, what does it mean?
- We have seen this message when the client attempted a /select query using a Solr Basic Auth credential that had Write role but not a Read role.
- We sometimes see this message when a Team Member attempts to access a SearchStax feature that is forbidden to users in that role.
- SearchStax deployments have the Configset API disabled by default. Attempts to use the API result in 403 errors.
- We have noticed occasional 403 errors while running the Sitecore Connector with Solr Basic Auth enabled on Azure deployments. The solution is to temporarily turn off Basic Auth.
Questions?
Do not hesitate to contact the SearchStax Support Desk.