Skip to content
Glue Docs

Application Integration Requirements

Application Integration Requirements for Data Collector

Section titled “Application Integration Requirements for Data Collector”

Overview

Section titled “Overview”

Before integrating applications with the Data Collector for User Access Review (UAR) campaigns, it’s essential to gather comprehensive information about each application’s user authentication and access data capabilities. This information helps determine the best integration approach and ensures successful data collection.

Information Gathering Process

Section titled “Information Gathering Process”

To streamline the integration process, we’ve created a standardized template to collect key information about your applications. This information focuses specifically on user login information and access data extraction capabilities.

Download the Template

Section titled “Download the Template”

📥 Download Application Integration Template (CSV)

Use this CSV template to document details for each application you plan to integrate with the Data Collector.

Required Information

Section titled “Required Information”

For each application, please provide the following information:

1. Application Name

Section titled “1. Application Name”
  • The name of the application or system
  • Example: Salesforce, SAP ERP, Custom CRM

2. Hosting Platform

Section titled “2. Hosting Platform”
  • The platform or infrastructure where the application is hosted
  • Example: AWS, Azure, Google Cloud, On-Premise VMware, Physical Server

3. Deployment Type

Section titled “3. Deployment Type”
  • Specify whether the application is cloud-based or on-premise
  • Options: Cloud, On-Premise, Hybrid

4. Current Access Data Extraction Method

Section titled “4. Current Access Data Extraction Method”
  • Describe how user access information is currently extracted (if at all)
  • Examples:
    • Manual CSV export
    • Automated reports
    • SQL queries
    • Active Directory group membership exports
    • Entra ID (Azure AD) group queries via Microsoft Graph API
    • PowerShell scripts pulling AD/Entra group memberships
    • LDAP queries for user attributes and group memberships
    • Not currently extracted

5. Access Granting Mechanism

Section titled “5. Access Granting Mechanism”
  • Describe how users are granted access to this application
  • This is important because if access is managed through directory groups, we can extract user information directly from those groups
  • Examples:
    • Active Directory (AD) security groups
    • Entra ID (Azure AD) security groups
    • Application-specific user management (internal database)
    • LDAP groups
    • Hybrid (both AD/Entra groups and application-specific roles)
    • Single Sign-On (SSO) with group-based access control
    • Manual user provisioning
  • If using AD or Entra groups, please specify:
    • Group names or naming conventions used for this application
    • Whether group membership directly maps to application roles/permissions

6. API Availability

Section titled “6. API Availability”
  • Does the application provide an API for extracting user information?
  • Options: Yes, No, Unknown
  • If yes, specify the API type: REST, SOAP, GraphQL, Other

7. SQL Query Access

Section titled “7. SQL Query Access”
  • Can user data be extracted directly via SQL queries?
  • Options: Yes, No, Unknown
  • If yes, do you have the necessary database access credentials?

8. Database Type (if applicable)

Section titled “8. Database Type (if applicable)”
  • If SQL access is available, specify the database platform
  • Options: MS SQL Server, Oracle, MySQL, PostgreSQL, MongoDB, Other

9. Multiple Roles Support

Section titled “9. Multiple Roles Support”
  • Can users have multiple roles within this application?
  • Options: Yes, No, Unknown
  • This helps determine how the data should be structured for UAR campaigns

10. Firewall Rules Required

Section titled “10. Firewall Rules Required”
  • Are firewall rules or network access controls required to enable Data Collector connectivity?
  • Options: Yes, No, Unknown
  • If yes, specify the IP addresses/ranges or ports that need to be allowed
  • This helps identify network configuration changes needed before integration

How to Complete the Template

Section titled “How to Complete the Template”
  1. Download the CSV template using the link above
  2. Open in a spreadsheet application (Excel, Google Sheets, etc.)
  3. Fill in one row per application you plan to integrate
  4. Be as detailed as possible in the description fields
  5. Save the completed template for your records

Submitting Your Requirements

Section titled “Submitting Your Requirements”

Once you’ve completed the template:

  1. Review the information to ensure accuracy and completeness
  2. Share with your integration team or Glue support contact

Best Practices

Section titled “Best Practices”

Be Thorough

Section titled “Be Thorough”

Even if you’re unsure about certain details, document what you know. Unknown information can be investigated during the integration planning phase.

Engage Application Owners

Section titled “Engage Application Owners”

Consult with application administrators or vendors to obtain accurate technical information about data extraction capabilities.

Consider Security Requirements

Section titled “Consider Security Requirements”

Note any security constraints or compliance requirements that may impact how user data can be accessed or extracted.

Document Access Permissions

Section titled “Document Access Permissions”

Identify who has the necessary permissions to configure APIs, database access, or other extraction methods.

Update Regularly

Section titled “Update Regularly”

As your application landscape changes, update the template to reflect new applications or changes to existing ones.