The LumApps connector allows you to integrate your LumApps intranet with Glean, enabling search and discovery of LumApps content directly within Glean. The connector indexes content pages, community pages, and posts, while strictly enforcing LumApps permissions so that users only see content they are authorized to access. All data is stored in your own Google Cloud Platform (GCP) project, ensuring you retain control and ownership of your data.

​
Supported Features and Limitations

The LumApps connector supports permissions-enforced indexing and search for a range of LumApps content types. It is designed to keep your Glean index in sync with LumApps, reflecting changes in content and permissions as quickly as possible.

​
Supported Objects/Entities

  • Content pages including homepages, directory listings, and custom content pages
  • Community pages
  • Community posts
For all indexed content, Glean processes and displays the title, last updated time, author, and text snippets in search results.

​
Supported API Endpoints/Features

  • LumApps API v1 for content, users, groups, and permissions.
  • If enabled, platform logs API for user activity .
  • OAuth 2.0 authentication for secure access.

​
Limitations

  • Only content visible to the admin user who authorizes the connector is indexed. Private pages not accessible to the admin will not be indexed.
  • Sections within a content page that have special permissions (different from the page default) are ignored and only content visible to the default groups is indexed.
  • Incremental crawls are not supported due to API limitations and full crawls are run at the same frequency as incremental crawls.
  • The Platform logs API for activity data is disabled by default and must be enabled by LumApps support if you want to use activity-based features.
  • Indexing of Spaces requires API v2, which is not currently supported.

​
Crawling Strategy

Crawl typeFull CrawlIncremental CrawlPeople DataActivityUpdate RateWebhookNotes
ContentYesNoNoNoFrequentNoAll content (pages, community pages, posts) fetched in parallel
IdentityYesNoYesNoFrequentNoUsers and groups fetched to determine permissions
ActivityNoNoNoYesOptionalNoRequires Platform logs API to be enabled by LumApps support
Crawls are performed using the admin access token, which has access to all content visible to the admin in the LumApps instance.

​
Requirements

To use the LumApps connector, you must meet certain technical, credential, and permission requirements. These ensure secure and complete access to your LumApps data for indexing and search.

​
Credential Requirements

  • OAuth 2.0 credentials: You must authorize Glean to access your LumApps instance using OAuth 2.0. This process provides Glean with a refresh token and an access token. The access token is used to fetch data from LumApps APIs and the refresh token is used to obtain new access tokens as needed.

​
Permission Requirements

  • The access token inherits the permissions of the admin user, so only content visible to that user will be indexed.
  • Glean enforces all LumApps permissions at query time, ensuring users only see content they are authorized to access.

​
Configuration and Setup Instructions

You configure and set up the LumApps connector primarily within the Glean workspace settings. The process involves authorizing access, specifying configuration options, and validating the connection.

​
Prerequisites

  • A LumApps instance with admin access. For more information, see LumApps Global administrator.
  • Glean deployment with access to Google Cloud Platform (GCP) for data storage.
  • LumApps API v1 enabled for your instance.
  • (Optional) Platform logs API enabled for activity data.
  • Be aware of your LumApps content and group permissions, as Glean will respect these settings exactly.

​
Step-by-Step Setup

Perform the following steps to connect LumApps connector to Glean:

​
Retrieving a temporary access token

  1. Go to your LumApps homepage.
  2. Right click and open Inspect Element for your browser and click the Console tab.
  3. Enter the following command in the Console to retrieve a temporary access token:
var instance=window.location.pathname.split('/');instance=instance[1]=="a"?instance[3]:instance[1];fetch(window.location.origin+"/service/init?customerHost="+window.location.host+"&instanceSlug="+instance).then(response=>response.text()).then(data=>{const match=data.match(/USER_ACCESS_TOKEN\s*=\s*'(.+?)'/);console.log(match&&match[1]?match[1]:data);}).catch(error=>console.error('Error fetching data:',error)); This command returns a long string, which represents a temporary access token. This token is used to fetch information about your LumApps instance. Use this when a Bearer access token is required.

​
Finding site information

Glean requires information on which LumApps sites to crawl. Follow the steps to find the site information:
  1. In the terminal, execute the following command:
curl 'https://sites.lumapps.com/_ah/api/lumsites/v1/instance/list' -H "Authorization: Bearer <your_temporary_access_token>" | jq
  1. If a 404 error is returned, your environment is not sites but something else (that is, the prefix in the domain name).
  2. Go to LumApps documentation.
  3. Go to the API server section, and substitute the different environment names until one succeeds. The environment names can be sites-us, sites-eu, csbx-us, or sites-ms for Microsoft customers.
  4. Navigate to the homepage of your LumApps site homepage. The URL looks like https://<site_name>.<your_company>.com and is the LumApps main production site which must be indexed.
  5. Enter the URL you got in step 4 in the Base URL input box.
    The URL must not contain any slashes after .com and must be only the base URL prefixed by https:// and ending in .com.
  6. On the LumApps homepage, use the Ctrl + / shortcut and navigate to the Advanced Debug info menu.
    To access the Advanced Debug info menu, you must be logged in as a global administrator.
  7. Copy and save the information like Customer ID, Instance IDs, User ID and Haussmann cell you see in the Advanced Debug info menu.

​
Creating an OAuth client for integration

Glean requires an OAuth application in LumApps to regularly refresh access tokens for the crawler. Glean follows the steps recommended by LumApps Oauth documentation.
  1. A global administrator can create an application by executing the following command. The Haussmann cell, Customer ID, temporary access token, and user ID are part of the arguments. An example of the haussmann cell is https://go-cell-001.api.lumapps.com
    Ensure the allowedUserIds field includes the quotes around the user ID.
curl -X POST <Haussmann_cell>/v2/organizations/<customer_id>/applications \ -H "Content-Type: application/json" \ -H "Authorization: Bearer <your_temporary_access_token>" \ -d '{"name":"Glean Search","scopes":["all.read"],"allowedUserIds":["<user_id>"]}' Command output: 
{
  "allowedUserIds": [
    "<User ID>"
  ],
  "clientSecret": "<Client Secret>",
  "createdBy": "<User ID>",
  "id": "<Application ID>",
  "name": "Glean Search",
  "scopes": ["all.read"],
  "status": "live",
}
  1. Copy and save the application ID and client secret with global administrator permissions.

​
Connecting LumApps connector with Glean

  1. Go to the Glean Admin console -> Data sources.
  2. Click Add data source -> Select LumApps.
  3. In the Setup tab, add the following information gathered in the previous sections:
    1. Add the environment information in Environment input box.
    2. Enter the customer ID in the Customer ID input box.
    3. Enter the instance ID in the Instance IDs input box.
    4. Enter the user ID in the User ID input box.
    5. Enter the Haussmann cell information in Haussmann cell input box. This API host is used to refresh access tokens. It must be in the form https://<customer_prefix>.api.lumapps.com.
  4. (Optional) Specify a greenlist of users who should have access to LumApps search results for testing before rolling out company-wide.
  5. (Optional) If you wish to power search within LumApps using Glean, refer to the Glean Embedded Search documentation for LumApps.

​
(Optional) Validating the setup

  1. In a terminal, execute the following command:
curl -X POST '<Haussmann_cell>/v1/content/list?lang=en&status=LIVE&instanceId=< id_of_production_site>&maxResults=1' -H "Authorization: Bearer <your_temporary_access_token>" | jq
  1. Get the value of the URL field and visit the following URL in your browser: <your_base_URL><value_of_url_field>
  2. If you get directed to a valid page in your LumApps instance, and the page matches the one returned by the API request in step 2, the setup is successful. If not, please contact the Glean engineer helping you with your deployment to figure out the issue.

​
Crawl Configuration Options

  • You can specify a greenlist of users to restrict access to LumApps search results during testing.
  • All content visible to the admin user is indexed and there are no redlist or custom object options at this time.
  • Crawl frequency is managed automatically to keep data fresh and full crawls are performed regularly due to API limitations.

​
Permissions & Security

Data and Metadata Ingested:
  • Content pages, community pages, community posts.
  • User and group information for permissions enforcement.
  • (Optional) Activity data if Platform logs API is enabled
Permission Propagation Logic:
  • Glean maps LumApps group and user permissions to enforce access controls at query time.
  • Only users with access to content in LumApps will see it in Glean search results.
Security & Compliance Notes:
  • All data is stored in a GCP project hosted by you, Glean and third parties cannot directly access your data.
  • OAuth 2.0 is used for secure authentication.
  • The connector does not support multi-instance scenarios or indexing of private pages not visible to the admin user.
Data Privacy Implications:
  • Your organization retains full control and ownership of all indexed data.
  • Glean enforces all LumApps permissions, ensuring data privacy and compliance with your internal policies.
If you have any issues or concerns, reach out to the Glean support team.