Clients often have deployments under multiple SLAs, where some deployments are under contract and others are billed to a credit card. Billing errors can sometimes occur and we will correct them as quickly as possible.

Be advised that credit-card refunds usually take about three banking days to get from us to you. We have no control over this delay.

The post Does SearchStax Issue Refunds? appeared first on SearchStax Docs.

SearchStax has you covered with robust Solr security features, including:

• Industry-standard security at the Solr cluster level and network level
• Environments secured with SSL out-of-the-box using Solr basic authentication
• Custom firewall rules to lock down search infrastructure to a whitelist of IPs
• Two-Factor Authentication (2FA) to increase log-on security
• Encryption in Transport to protect the integrity and security of transmissions
• Encryption at Rest to ensure data is encrypted while on disk
• Regular quarterly scans to identify and patch any Apache Solr vulnerabilities

We protect your Solr environment and data with:

• Authentication and authorization – to control who has access to your Solr instances
• Transport security – to protect communication between the Solr service and client applications
• Secure configuration access – to ensure configuration files are only accessible to authorized users
• Restricted API access – to authorized users through firewalls, IP whitelisting and access control lists
• Monitor logs – to regularly identify and respond to security incidents and suspicious events
• Patches and security updates – to keep Solr up-to-date with the latest updates and vulnerabilities

What Solr security features are add-ons?

These security features are available as additional add-ons:

• Single Sign-On
• Private networking
• HIPAA ready
• Incident RCAs
• Priority patching
• Monthly vulnerability scans

Talk with your Account Manager or sales representative to learn more about security add-ons.

How does SearchStax implement SSO?

SSO provides a frictionless user experience by allowing a user to sign on to a SearchStax application using the same credentials they use for other applications within their company. The use of SSO enforces risk-based access policies and automates provisioning workflows and enables self-service tools to help companies reduce IT costs.

Our SSO uses the Microsoft Azure Active Directory and open standard Security Assertion Markup Language (SAML) to pass authorization credentials to service providers.

Additional Information

See these additional information sources:

• Solr Security
• Securing Deployments in SearchStax Managed Search

Questions?

Do not hesitate to contact the SearchStax Support Desk.

The post What Solr security features does SearchStax provide? appeared first on SearchStax Docs.

Legacy Gold SLAs will still be honored. If you have any questions, contact your Account Manager.

Questions?

Do not hesitate to contact the SearchStax Support Desk.

The post What happened to Gold SLAs? appeared first on SearchStax Docs.

We take this precaution because Zookeeper doesn’t require authentication. Anyone who can guess your Zookeeper endpoint can use zkcli.sh/.bat to make malicious changes to your deployment’s configuration files. Even worse, there are no logs of such meddling. You can’t tell who changed the files.

As a further precaution, we have modified the Managed Search IP Filtering controls to prohibit giving the Zookeeper ensemble a 0.0.0.0/0 filter.

Secure Zookeeper Access

The SearchStax API includes a rich set of methods for remote management of SearchStax Managed Search deployments. One small part of that is a set of five secure Zookeeper methods:

• list: Returns a list of named configurations from a Zookeeper ensemble.
• create: Creates/uploads a configset to the Zookeeper ensemble.
• read: Returns a list of config files from a configuration in the Zookeeper ensemble.
• delete: Deletes a configset from the Zookeeper ensemble.
• download: Downloads a configset from the Zookeeper ensemble.

Your API Key authorizes these actions on each of the associated deployments. Each link leads to full syntax and examples in both Bash and PowerShell.

Ask Us for an API Key

An API Key is a persistent authorization key that gives you access to one or more specific deployments. The key itself is a long string of random-looking characters. One API Key can cover multiple deployments in the same account. Each deployment may be associated with only one API Key.

You can use the SearchStax API to generate your own API Key, but that is an involved process. To save you time, SearchStax Support will be happy to create an API Key for you:

1. Make a list of the deployments you’d like to access with your API Key. Use the deployment ID numbers (ss123456) to identify the deployments.
2. Contact SearchStax Support. Give us the list of deployments.

Questions?

Do not hesitate to contact the SearchStax Support Desk.

The post How can I secure Zookeeper for Solr deployments? appeared first on SearchStax Docs.

For Managed Search, see the Asking for Help page. If you are using Site Search, see the similar Asking for Help page.

If you can’t log in, you can send an email message to the SearchStax Support Desk or use our corporate Contact Us page.

Questions?

Do not hesitate to contact the SearchStax Support Desk.

The post Asking for Help appeared first on SearchStax Docs.

You may optionally copy these alerts to your PagerDuty account for realtime alerting. See PagerDuty Solr Integration.

The post Can SearchStax Managed Search integrate with PagerDuty? appeared first on SearchStax Docs.

The post Can I Add New Relic Analytics to SearchStax Managed Search? appeared first on SearchStax Docs.

Self-service SiLK integration with SearchStax Managed Search has been phased out. If your system demands SiLK integration, we can discuss it as part of a premium support agreement or consulting contract.

The post Can I use SiLK with SearchStax Managed Search Solr? appeared first on SearchStax Docs.

• Drupal 7 works with Solr versions up to 5.4.1, and can be adapted to use Solr 7.x.
• Drupal 8 integrates with more recent versions of Solr. (Our testing used Solr 6.4.2 with Drupal 8)
• Drupal 9 using Drupal’s Search API and its Search API Solr modules (we tested with Drupal 9.5.11 and Solr 8.11.2)
• Drupal 10 using Drupal’s Search API and its Search API Solr modules (we tested with Drupal 10.1.4 and Solr 8.11.2)

In addition, SearchStax recently announced the availability of a Drupal Module that integrates SearchStax Site Search running on Apache Solr 8 with a Drupal 8 or 9 environment.

At a deeper level, the version of Solr doesn’t depend on the version of Drupal. Rather it depends on the version of the Drupal Search API Solr module. The Search API Solr 4.2.x supports Solr 3.6 to 8.x. Search API Solr 4.2.x can be installed in Drupal 7, 8, 9, and 10.

The post What Versions of Drupal Does SearchStax Support? appeared first on SearchStax Docs.

The post Does SearchStax Managed Search integrate with Django Haystack? appeared first on SearchStax Docs.