Google Search Appliance Connectors

Similar documents
Google Search Appliance Connectors

Google Search Appliance Connectors

Google Search Appliance Connectors

Google Search Appliance Connectors

Google Search Appliance Connectors

Google Search Appliance Connectors

Google Search Appliance Connectors

Google Search Appliance Connectors

Google Search Appliance Connectors

BLUEPRINT TEAM REPOSITORY. For Requirements Center & Requirements Center Test Definition

Setting Up Resources in VMware Identity Manager. VMware Identity Manager 2.8

Setting Up Resources in VMware Identity Manager (On Premises) Modified on 30 AUG 2017 VMware AirWatch 9.1.1

VMware AirWatch Content Gateway for Linux. VMware Workspace ONE UEM 1811 Unified Access Gateway

Assuming you have Icinga 2 installed properly, and the API is not enabled, the commands will guide you through the basics:

MARWATCH INSTALLATION AND UPGRADE GUIDE

VMware AirWatch Content Gateway Guide for Linux For Linux

Coveo Platform 7.0. Oracle UCM Connector Guide

Setting Up Resources in VMware Identity Manager

Migrating vrealize Automation 6.2 to 7.2

VMware AirWatch Content Gateway for Windows. VMware Workspace ONE UEM 1811 Unified Access Gateway

Oracle Enterprise Manager. 1 Before You Install. System Monitoring Plug-in for Oracle Unified Directory User's Guide Release 1.0

VMware Identity Manager Administration

Installing and Configuring vcloud Connector

VMware Identity Manager Connector Installation and Configuration (Legacy Mode)

Installing and Configuring VMware Identity Manager Connector (Windows) OCT 2018 VMware Identity Manager VMware Identity Manager 3.

VMware AirWatch Content Gateway Guide for Windows

Google Search Appliance

NotifySCM Workspace Administration Guide

Google Search Appliance

Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface

Configuring SAML-based Single Sign-on for Informatica Web Applications

Access SharePoint using Basic Authentication and SSL (via Alternative Access URL) with SP 2016 (v 1.9)

Hitachi ID Systems Inc Identity Manager 8.2.6

Contents Overview... 5 Downloading Primavera Gateway... 5 Primavera Gateway On-Premises Installation Prerequisites... 6

Realms and Identity Policies

Oracle Oracle Identity Manager 11g

ENTRUST CONNECTOR Installation and Configuration Guide Version April 21, 2017

Avalanche Remote Control User Guide. Version 4.1

SAML-Based SSO Configuration

Installation Guide for Pulse on Windows Server 2012

Workspace ONE UEM Certificate Authentication for Cisco IPSec VPN. VMware Workspace ONE UEM 1810

Realms and Identity Policies

Installation on Windows Server 2008

Synchronizer Quick Installation Guide

Cisco Unified Serviceability

VMware Identity Manager Cloud Deployment. DEC 2017 VMware AirWatch 9.2 VMware Identity Manager

VMware Identity Manager Cloud Deployment. Modified on 01 OCT 2017 VMware Identity Manager

INSTALLING ADOBE LIVECYCLE WORKBENCH 11

Setting Up Resources in VMware Identity Manager (SaaS) Modified 15 SEP 2017 VMware Identity Manager

TIBCO LiveView Web Getting Started Guide

VMware Content Gateway to Unified Access Gateway Migration Guide

VMware Enterprise Systems Connector Installation and Configuration. JULY 2018 VMware Identity Manager 3.2 VMware Identity Manager VMware AirWatch 9.

Enterprise Vault.cloud CloudLink Google Account Synchronization Guide. CloudLink to 4.0.3

Cisco TelePresence Management Suite Provisioning Extension

Installing and Configuring vcloud Connector

VMware Identity Manager Administration. MAY 2018 VMware Identity Manager 3.2

IBM Security Identity Governance and Intelligence. SDI-based IBM Security Privileged Identity Manager adapter Installation and Configuration Guide IBM

Wavelink Avalanche Site Edition Java Console User Guide. Version 5.3

VMware Skyline Collector Installation and Configuration Guide. VMware Skyline 1.4

Server Installation Guide

MULTI FACTOR AUTHENTICATION USING THE NETOP PORTAL. 31 January 2017

Upgrading an ObserveIT One-Click Installation

VMware AirWatch Content Gateway Guide for Windows

Realms and Identity Policies

Using vrealize Operations Tenant App as a Service Provider

Logging into the Firepower System

Edge Device Manager Quick Start Guide. Version R15

HP-UX for the Itanium Processor Family Architecture. 215 MB Approx

FUSION REGISTRY COMMUNITY EDITION SETUP GUIDE VERSION 9. Setup Guide. This guide explains how to install and configure the Fusion Registry.

Table of Contents. About this Guide..3. This workis licensed under a Creative Commons Attribution 2.5 License. Getting Help..4. Welcome to Pinnacle..

VMware AirWatch Content Gateway Guide for Windows

VMware AirWatch Content Gateway Guide For Linux

VMware AirWatch Content Gateway Guide for Windows

Automation Anywhere Enterprise 10 LTS

Installing and Configuring vcenter Multi-Hypervisor Manager

Extended Search Administration


VMware AirWatch Certificate Authentication for Cisco IPSec VPN

Registering Search Interface to SAS Content as Google OneBox Module

Policy Manager for IBM WebSphere DataPower 7.2: Configuration Guide

Enabling SAML Authentication in an Informatica 10.2.x Domain

Directory Integration with VMware Identity Manager

SafeConsole On-Prem Install Guide. version DataLocker Inc. July, SafeConsole. Reference for SafeConsole OnPrem

Best Practices for Security Certificates w/ Connect

HPE Security ArcSight Connectors

BUILD AND DEPLOY SOA PROJECTS FROM DEVELOPER CLOUD SERVICE TO ORACLE SOA CLOUD SERVICE

SAML-Based SSO Configuration

VMware AirWatch Remote Management Guide Installing, configuring, and using the Remote Management Service

Technology Note. ER/Studio: Upgrading from Repository (v ) to Team Server 2016+

QUICKSTART GUIDE: THE ATTIVIO PLATFORM


Signing In to WebEx Assistant, page 1

IBM Atlas Policy Distribution Administrators Guide: IER Connector. for IBM Atlas Suite v6

Upgrading Big Data Management to Version Update 2 for Hortonworks HDP

CA LISA. Installation and Configuration Guide. Version 7.0.2

Deploying VMware Identity Manager in the DMZ. JULY 2018 VMware Identity Manager 3.2

VMware Skyline Collector Installation and Configuration Guide. VMware Skyline Collector 2.0

ECM-VNA Convergence Connector

Red Hat CloudForms 4.6

VMware AirWatch Certificate Authentication for EAS with ADCS

Transcription:

Google Search Appliance Connectors Deploying the Connector for SharePoint User Profiles Google Search Appliance Connector for SharePoint User Profiles software version 4.1.1 Google Search Appliance software versions 7.4 and 7.6 January 2017

Table of Contents About this guide Overview of the GSA Connector for SharePoint User Profiles Automatic updates every 15 minutes Supported SharePoint versions Supported operating systems for the connector Supported authentication mechanisms Known connector limitation CPU and memory recommendation Before you deploy the Connector for SharePoint User Profiles Deploy the Connector for SharePoint User Profiles Step 1 Configure the search appliance Add the URL Add the IP address Create and configure a collection Set up security Step 2 Install the Connector for SharePoint User Profiles Windows Installation Command-line installation for Linux or Windows HTTPS configuration Step 3 Configure adaptor-config.properties variables Step 4 Run the Connector for SharePoint User Profiles Uninstall the Google Search Appliance Connector for SharePoint User Profiles Troubleshoot the Connector for SharePoint User Profiles

About this guide This guide is intended for anyone who needs to deploy the Google Search Appliance Connector 4.1.1 for SharePoint User Profiles. The guide assumes that you are familiar with Windows or Linux operating systems and configuring the Google Search Appliance by using the Admin Console. See the Google Search Appliance Connectors Administration Guide for general information about the connectors, including: What s new in Connectors 4? General information about the connectors, including the configuration properties file, supported ACL features, and other topics Connector security Connector logs Connector Dashboard Connector troubleshooting For information about using the Admin Console, see the Google Search Appliance Help Center. For information about previous versions of connectors, see the Connector documentation page in the Google Search Appliance Help Center.

Overview of the GSA Connector for SharePoint User Profiles The Connector for SharePoint User Profiles enables you to crawl and index information about users in the SharePoint User Profile Service Application. Once the search appliance has indexed this information, it can use it in the expert search feature. Expert search enables your users to find experts in your organization by searching on keywords. For detailed information about this feature, see the help page for Search > Search Features > Expert Search. A single instance of the Connector for SharePoint User Profiles can have GSA index a single SharePoint web application. Each SharePoint web application can share the same SharePoint User Profile Service application. The following diagram provides an overview of how the search appliance gets content (user profiles) from SharePoint through the connector. For explanations of the numbers in the process, see the steps following the diagram. 1. The Connector for SharePoint User Profiles starts communicating with the repository by presenting authentication credentials. 2. The repository sends Doc IDs of documents in the repository to the connector. 3. The connector constructs URLs from the Doc IDs and pushes them to the search appliance in a metadata-and-url feed. Take note that this feed does not include the document contents. 4. The search appliance gets the URLs to crawl from the feed.

5. The search appliance crawls the repository according to its own crawl schedule, as specified in the GSA Admin Console. It crawls the content by sending GET requests for content to the connector. 6. The connector requests the content from the repository. 7. The repository sends the content to the connector. 8. The connector pushes the content to the search appliance for indexing. Automatic updates every 15 minutes After the initial process completes, the connector periodically informs the search appliance of new documents and changed documents, according to the value set in the connector configuration option adaptor.incrementalpollperiodsecs. The default interval value is 15 minutes, but you can configure it to suit your needs. For more information, see Common configuration options in the Administration Guide. Supported SharePoint versions The Connector for SharePoint User Profiles 4.1.1 supports the following SharePoint versions: SharePoint 2016 SharePoint 2013 SharePoint 2010 Supported operating systems for the connector The Connector for SharePoint User Profiles 4.1.1 must be installed on one of the following supported operating systems: Windows Server 2012 Windows Server 2008 (32 and 64 bit) Windows Server 2003 (32 and 64 bit) Ubuntu Red Hat Enterprise Linux 5.0 SUSE Enterprise Linux 10 (64 bit)

Supported authentication mechanisms The Connector for SharePoint User Profiles 4.1.1 supports any authentication mechanism where a verified user ID is rendered. Known connector limitation Supports one connector instance per User Profile Service Application instance. CPU and memory recommendation The recommended configuration for the Connector for SharePoint User Profiles is 4 GB RAM and 4 core CPU.

Before you deploy the Connector for SharePoint User Profiles Before you deploy the Connector for SharePoint User Profiles, ensure that your environment has all of the following required components: GSA software version 7.2.0.G.264 or higher To download GSA software, visit the Google for Work Support Portal (password required). Java JRE 1.7u9 or higher installed on computer that runs the connector. If you want to use the DH (Diffie-Hellman) style of encryption and you are running the GSA with 2048-bit encryption, JRE 1.7u80 or 1.8.0_20 is required. Connector for SharePoint User Profiles 4.1.1 JAR executable For information about finding the JAR executable, see Step 2 Install the Connector for SharePoint User Profiles. User account for the connector, with Full Control permissions to SharePoint User Profile Service Application If running the connector on Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012 machine, specify the LAN Manager Authentication Level Policy. Optionally, configure the search appliance for the authentication method in use (typically LDAP for Active Directory). For detailed information about configuring authentication, see Managing Search for Controlled Access-Content.

Deploy the Connector for SharePoint User Profiles Because the Connector for SharePoint User Profiles is installed on a separate host, you must establish a relationship between the connector and the search appliance. To deploy the Connector for SharePoint User Profiles, perform the following tasks: 1. Configure the search appliance 2. Install the Connector for SharePoint User Profiles 3. Optionally, configure adaptor-config.properties variables 4. Run the Connector for SharePoint User Profiles Step 1 Configure the search appliance For the search appliance to work with the Connector for SharePoint User Profiles, the search appliance needs to be able to crawl information about users in the SharePoint User Profile Service Application via connector and accept feeds from the connector. Once indexed by the search appliance, SharePoint User Profile information has to reside in a collection that contains only profile information. To set up these capabilities, perform the following tasks by using the search appliance Admin Console: 1. Add the URL provided by the connector to the search appliance s follow patterns. 2. Add the IP address of the computer that hosts the connector to the list of Trusted IP addresses so that the search appliance will accept feeds from this address. 3. Create and configure a collection for user profile information. 4. Set up security. Add the URL To add the URLs provided by the connector to the search appliance s crawl configuration follow patterns: 1. In the search appliance Admin Console, click Content Sources > Web Crawl > Start and Block URLs. 2. Under Follow Patterns, add the URL that contains the hostname of the machine that hosts the connector and the port where the connector runs. For example, you might enter http://connector.example.com:5678/doc/ where connector.example.com is the hostname of the machine that hosts the connector. By default the connector runs on port 5678. 3. Click Save.

Add the IP address To add the IP address of the computer that hosts the connector to the list of trusted IP addresses: 1. In the search appliance Admin Console, click Content Sources > Feeds. 2. Under List of Trusted IP Addresses, select Only trust feeds from these IP addresses. 3. Add the IP address for the connector to the list. 4. Click Save. Create and configure a collection To create and configure a collection for user profile information: 1. In the search appliance Admin Console, click Index > Collections. 2. In the Create New Collection section, enter a unique name for the new collection. 3. For Initial Configuration, select Empty and click Create. 4. In the Current Collections section, click Edit for the newly-created user profile collection. 5. In the Include Content Matching the Following Patterns box, add the URL pattern for the connector, for example http://connector.example.com:5678/doc/. 6. Configure the default_collection to exclude user profile documents. In the Current Collections section, click Edit for default_collection. 7. In the Do Not Include Content Matching the Following Patterns box, add the URL pattern for the connector (see step 5). 8. Click Save. Set up security For information about setting up security, see Enable connector security in the Administration Guide.

Step 2 Install the Connector for SharePoint User Profiles This section describes the installation process for the Google Search Appliance Connector for SharePoint User Profiles on the connector host computer. This connector version does not support installing the connector on the Google Search Appliance. You can install the Connector for SharePoint User Profiles on any host running one of the supported operating systems. As part of the installation procedure, you need to edit some configuration variables in the configuration file. Take note that you can encrypt the value for sharepoint.password before adding it to the file by using the Connector Dashboard or standalone command line program, as described in Encode sensitive values, in the Administration Guide. Windows Installation To install the Connector for SharePoint User Profiles on Windows: 1. Log in to the computer that will host the connector by using an account with sufficient privileges to install the software. 2. Start a web browser. 3. Visit the connector 4.1.1 software downloads page at http://googlegsa.github.io/adaptor/index.html. Download the exe file by clicking on Microsoft SharePoint User Profiles in the Windows Installer table. You are prompted to save the single binary file, spup-install-4.1.1.exe. 4. Start installing the file by double clicking spup-install-4.1.1. 5. On the Introduction page, click Next. 6. On the GSA Hostname and other required configuration values page, enter values for the following options: a. GSA Hostname or IP address of the GSA that will use the connector. For example, enter yourgsa.example.com b. SharePoint Server. For example, enter http://yoursharepoint.example.com/ c. Adaptor port number for any crawlable documents this connector serves. Each instance of a Connector on same machine requires a unique port. The default is 5778.

d. Server dashboard port for the Connector Dashboard. The value is the port on which to view web page showing information and diagnostics about the connector. The default is 5779. You can edit this value and set it to any value that is different from the Adaptor port number (server.port). e. Enter the Maximum Java Heap size (in megabytes). Default is 1024. f. Whether or not to run the connector after the installer finishes. 7. Click Next. 8. On the Choose Install Folder page, accept the default folder or navigate to the location where you want to install the connector files. 9. Click Next. 10. On the Choose Shortcut Folder, accept the default folder or select the locations where you want to create product icons. 11. To create icons for all users of the Windows machine where you are installing the connector, check Create Icons for All Users and click Next. 12. On the Pre-Installation Summary page, review the information and click Install. The connector Installation process runs. 13. On the Install Complete page, click Done. If you selected the option to run the connector after the installer finishes, the connector starts up in a separate window. When SharePoint and the current user domain is the same or from the same domain hierarchy, Windows operating systems automatically use the credentials of the person currently signed on to Windows. If not, you need to specify a username and password. For example, suppose that you run the connector from a coprorate domain such as @mycompany.com against a SharePoint instance from another domain, such as GSA-CONNECTORS. In this case, you need to specify user credentials for GSA-CONNECTORS domain. 14. If the adaptor needs to use Live Authentication to connect to SharePoint, then add these additional configuration options to adaptor-config.properties: sharepoint.username=adaptoruser Live Authentication Id sharepoint.password=us3r_password sharepoint.useliveauthentication=true

15. If the adaptor needs to use ADFS Authentication to connect to SharePoint, then add these additional configuration options to adaptor-config.properties: sharepoint.username=adaptoruser@yourdomain.com sharepoint.password=us3r_password sharepoint.sts.endpoint=https://adfs.example.com/adfs/services/trust/20 05/usernamemixed sharepoint.sts.realm=urn:myserver:sharepoint or https://yoursharepoint.example.com/_trust Command-line installation for Linux or Windows The following procedure gives the steps for installing the Connector for SharePoint User Profiles on Linux. Take note that if you prefer not to use the Windows installer, you can also follow this procedure to install the Connector on Windows. To install the connector: 1. Download the Connector for SharePoint User Profiles JAR executable (adaptorsharepoint-user-profile-4.1.1-withlib.jar) from http://googlegsa.github.io/adaptor/index.html. 2. Create a directory on the host where the connector will reside. For example, create a directory called sharepointup-connector_411. 3. Copy the Connector for SharePoint User Profiles 4.1.1 JAR executable to the directory. 4. Create an ASCII or UTF-8 file named adaptor-config.properties in the directory that contains the connector binary. 5. Provide the following configuration (replacing bolded items with your real configuration) within the file: gsa.hostname=yourgsa.example.com or IP address sharepoint.server=http://yoursharepoint.example.com/ where the value of yoursharepoint.example.com is a fully-qualified domain name. If it is not a fully-qualified domain name, then you must set DNS override on the connector host.

6. Linux: Add these additional configuration options to adaptorconfig.properties: sharepoint.username=yourdomain\\connectoruser sharepoint.password=user_password Windows: When SharePoint and the current user domain is the same or from same domain hierarchy, Windows operating systems automatically use the credentials of the person currently signed on to Windows. If not, you need to specify a username and password. For example, suppose that you run the connector from a coprorate domain such as @mycompany.com against a SharePoint instance from another domain, such as GSA-CONNECTORS. In this case, you need to specify user credentials for GSA-CONNECTORS domain. 7. Create an ASCII or UTF-8 file named logging.properties in the same directory that contains the connector binary and add the following content: handlers = java.util.logging.filehandler.level = WARNING com.google.enterprise.adaptor.level = INFO com.google.enterprise.adaptor.sharepoint.level = INFO java.util.logging.filehandler.formatter=com.google.enterprise.adaptor. CustomFormatter java.util.logging.filehandler.pattern=logs/spup-adaptor.%g.log java.util.logging.filehandler.limit=104857600 java.util.logging.filehandler.count=20 8. Create a folder named logs in the same directory. Windows: When SharePoint and the current user domain is the same or from the same domain hierarchy, Windows operating systems automatically use the credentials of the person currently signed on to Windows. If not, you need to specify a username and password. For example, suppose that you run the connector from a coprorate domain such as @mycompany.com against a SharePoint instance from another domain, such as GSA-CONNECTORS. In this case, you need to specify user credentials for GSA-CONNECTORS domain.

9. Get a SharePoint certificate to add it as a trusted host for the connector by performing the following steps: a. Navigate to SharePoint in a browser. A warning page appears with a message such as "This Connection is Untrusted." This message appears because the certificate is self-signed and not signed by a trusted Certificate Authority. b. Click, "I Understand the Risks" and "Add Exception." c. Wait until the "View..." button is clickable, then click it. d. Change to the "Details" tab and click "Export...". e. Save the certificate in your connector's directory with the name "sharepoint.crt". f. Click Close and Cancel to close the windows. 10. To allow the connector to trust SharePoint, enter the following command: keytool -importcert -keystore cacerts.jks -storepass changeit -file sharepoint.crt -alias sharepoint 11. When prompted Trust this certificate?, answer yes. 12. If the adaptor needs to use Live Authentication to connect to SharePoint, then add these additional configuration options to adaptor-config.properties: sharepoint.username=adaptoruser Live Authentication Id sharepoint.password=us3r_password sharepoint.useliveauthentication=true 13. If the adaptor needs to use ADFS Authentication to connect to SharePoint, then add these additional configuration options to adaptor-config.properties: sharepoint.username=adaptoruser@yourdomain.com sharepoint.password=us3r_password sharepoint.sts.endpoint=https://adfs.example.com/adfs/services/trust/20 05/usernamemixed sharepoint.sts.realm=urn:myserver:sharepoint or https://yoursharepoint.example.com/_trust

HTTPS configuration If SharePoint is configured to use HTTPS, get a SharePoint certificate to add it as a trusted host for the connector by performing the following steps: 1. Navigate to SharePoint in a browser. A warning page appears with a message such as "This Connection is Untrusted." This message appears because the certificate is self-signed and not signed by a trusted Certificate Authority. 2. Click, "I Understand the Risks" and "Add Exception." 3. Wait until the "View..." button is clickable, then click it. 4. Change to the "Details" tab and click "Export...". 5. Save the certificate in your connector's directory with the name "sharepoint.crt". 6. Click Close and Cancel to close the windows. 7. To allow the connector to trust SharePoint, enter the following command: keytool -importcert -keystore cacerts.jks -storepass changeit -file sharepoint.crt -alias sharepoint 8. When prompted Trust this certificate?, answer yes. Step 3 Configure adaptor-config.properties variables Optionally, you can edit or add additional configuration variables to the adaptorconfig.properties file. The following table lists the most important variables that pertain to the SharePoint User Profiles connector, as well as their default values. See also Common configuration options in the the Administration Guide. Variables Description Default server.dashboardport server.port Port on which to view web page showing information and diagnostics. Unique value for the retriever port. The Windows installer sets this value to 5779. If you use the command-line installer, this value defaults to 5679 for all adaptors. You can edit this value and set it to any value that is different from server.port. The Windows installer sets this value to 5778. If you use

adaptor.namespace profile.setacl profile.mysitehost Namespace used for ACLs sent to GSA. Whether user profile information is considered restricted to authenticated users or public. SharePoint Web application URL hosting my sites for users. the command-line installer, this value defaults to 5678. You can edit this value. Default True Virtual server Step 4 Run the Connector for SharePoint User Profiles After you install the Connector for SharePoint User Profiles, you can run it by using cmd.exe on the host machine: java -Djava.util.logging.config.file=logging.properties -jar adaptorsharepoint-user-profile-4.1.1-withlib.jar Verify that the connector has started and is running by navigating to the Connector Dashboard at http://<connector_host>:<nnnn>/dashboard or https://<connector_host>:<nnnn>/dashboard where <nnnn> is the number you specified as the value for the server.dashboardport in the configuration file. To run the connector as a service, use the Windows service management tool or run the prunsrv command, as described in Run a connector as a service on Windows in the Administration Guide.

Uninstall the Google Search Appliance Connector for SharePoint User Profiles If you have created a Windows Service for the Connector for SharePoint User Profiles, before you uninstall the connector, you must remove the Windows Service. To stop and remove the Windows Service, execute the following command: prunsrv //DS//adaptor-sharepoint-user-profile To uninstall the Connector for SharePoint User Profiles on Windows: 1. Navigate to the SharePoint User Profiles connector installation folder, _GSA_SPUP_Adaptor_installation. 2. Click Uninstall_GSA_SPUP_Adaptor.exe. The Uninstall GSA_SPUP_Adaptor page appears. 3. Click Uninstall. Files are uninstalled. 4. Click Done.

Troubleshoot the Connector for SharePoint User Profiles For information about troubleshooting the Connector for SharePoint User Profiles, see Troubleshoot Connectors, in the Administration Guide.