Information for: DEVELOPERS   PARTNERS

Optional add-on offerings Product Guide

Last updated: July 14, 2020

Acquia will provide the services described below only if purchased by Customer, as indicated in the Order.

1. Multi-Region Replication With Failover

The Acquia Multi-Region service is an extension of Acquia Cloud Platform Enterprise and is limited to one Code Base. Fees for this service cover environment and application set up preparation, ongoing support and operational service, coordination and restoration of service during outages, and development on improving the service. Multi Region Failover requires Customers to use a third party CDN to achieve failover in the event of primary Region loss. Customer is responsible for performing the failover upon Acquia’s recommendation during a Region outage. Customer may be required to implement Acquia recommended application changes to ensure optimal Multi Region Service and support. Customer must provide Acquia with at least five business days advance notice before electing to add an additional Code Base to this service.

2. Acquia Search Dedicated Instance

Acquia will provide Customer with the Acquia Search Dedicated instance, which provides an isolated, hosted search environment for its website(s) that is totally dedicated to a particular Customer. Dedicated Search includes the following:

  • The ability to scale queries and index size beyond limits available on shared search
  • A 99.95% uptime in accordance with Acquia’s Service Level Policy
  • Ability for Customer to perform load tests
  • Option to deploy other Solr libraries (Customer must test libraries locally)
  • The ability for Customer to provision additional indexes to support multiple search use cases

3. Single Sign-On – Drupal SAML/LDAP Configuration

The goal of the Single Sign-On (SSO)–Drupal SAML/LDAP configuration engagement is to assist customers in making the correct changes to the SimpleSAMLphp configuration that allows their Drupal site to work correctly with their SAML 2.0 compliant Identity Provider (IdP). This engagement isn’t meant as a replacement for the Customer involvement in the configuration. Acquia will assist the Customer’s Drupal team and coordinate with Customer’s identity provider team in the configuration of SimpleSAML/LDAP federated login services as a package available in small, medium, large, and extra-large options, depending on the size and complexity of Customer’s Drupal project. The SimpleSAMLphp engagement offering is limited to ensuring the implementation of a standard configuration that allows Drupal to authenticate against the customer’s IdP. This process requires that the customer either already have an IdP, or have someone available during the engagement with knowledge of how their IdP is configured. While the platform supports IdP first-flow or IdP initiated authentication, Acquia has limited visibility into these configurations. This offering assumes Service Provider (SP) initiated authentication. With SP initiated, Acquia can more thoroughly test the application from the SP side and view the corresponding logs.

The SimpleSAMLphp offering isn’t a general single sign-on solution. It doesn’t cover customizing the interaction between Drupal and the IdP or the ability to shape and use the data returned by the IdP other than to the use the simpleSAMLphp Authentication Drupal module to allow Drupal users to be created and authenticated by the IdP.

3.1 Requirements

  • The customer has one or more SAML 2.0 compliant IdPs identified and lined up.
  • The customer can identify a primary technical contact at each IdP.
  • The customer will use SimpleSAMLphp for the SP and the SimpleSAMLphp Authentication module to integrate with Drupal.

3.2 Acquia responsibilities

  • Install and configure SimpleSAMLphp and the SimpleSAMLphp Authentication module to communicate with the customer’s chosen IdP.
  • Assist and advise with troubleshooting SimpleSAMLphp to function against customer’s identified IdPs, including coordinating developer and IdP technical resources.
  • Perform the following services for the number of sites based on the engagement package:
    • Each of a customer’s Dev, Stage, and Prod environments count as a separate site. If the customer wants all three of these to authenticate against their IdP, that would account for three sites.
    • In a Drupal multisite, each of websites will count three times towards the total number of sites for the Acquia packaged engagement–that’s, multisite with three sites within it on three environments (Dev, Stage, Prod) totals to nine sites for purposes of the Acquia packaged engagement.
  • Coordination will occur with the use of Acquia’s ticketing system.
  • Acquia may provide one coordination conference call per site. If the customer purchases a small engagement, Acquia will participate in up to three coordination calls. If the customer purchases a large engagement, Acquia will participate in up to nine coordination calls.
  • Collaborate with the Customer technical resources for the testing of the SimpleSAMLphp configuration

3.3 Customer responsibilities

  • Obtain and install SP metadata at the IdP.
  • Collaborate with Acquia technical resources for the testing of the SimpleSAMLphp configuration.
  • Ensure the availability of technical resources with access to and knowledge of the IdP.
  • Own all custom code and testing of custom workflows beyond what’s provided by the SimpleSAMLphp Authentication Drupal module and the SimpleSAMLphp library.
  • Own testing and validation of all Drupal configurations and workflows that integrate with simpleSAMLphp Authentication module functionality (including custom role assignments and cookie based redirection).