LightBeam Documentation
Installer GuidesData SourcesPlaybooksInsightsPrivacyOpsGovernance
  • 💡What is LightBeam?
  • 🚀Getting Started
    • ⚙️Installer Guides
      • Pre-Requisites / Security Configurations
        • Firewall Requirements
        • Securing LightBeam on EKS with AWS Certificate Manager on Elastic Load Balancer
        • Configure HTTPS for LightBeam Endpoint FQDN Standalone deployment
        • Using Custom Certificates with LightBeam
        • Securing LightBeam on GKE with Google Certificate Manager and GCE Ingress
      • Core
        • LightBeam Deployment Instructions
        • LightBeam Installer
        • Web App Deployment
        • LightBeam Diagnostics
        • LightBeam Cluster Backup & Restore using Velero
      • Platform Specific
        • AWS
        • Microsoft Azure
        • Google Cloud (GKE)
        • Standalone Virtual Machine
        • Deployment on an Existing Managed Kubernetes Cluster
        • Azure Marketplace Deployment
      • Integration and Setup
        • Setting Up AWS PrivateLink for RDS-EKS Interaction
        • Twingate and LightBeam Integration Guide
        • Data Subject Request Web Application Server
        • Generate CSR for LightBeam
  • 🧠Core Features
    • 🔦Spectra AI
      • 🔗Data Sources
        • Cloud Platforms
          • AWS Auto Discovery
          • GCP Auto Discovery
        • Databases and Datalakes
          • PostgreSQL
          • Aurora (PostgreSQL)
          • Snowflake
          • MS SQL
          • MySQL
          • Aurora (MySQL)
          • BigQuery
          • AWS Redshift
          • Oracle
          • DynamoDB
          • MongoDB
          • CosmosDB (PostgreSQL)
          • CosmosDB (MongoDB)
          • CosmosDB (NoSQL)
          • Looker
          • AWS Glue
          • Databricks
          • SAP HANA
          • CSV Files as a Datasource
        • Messaging
          • Gmail
          • Slack
          • MS Teams
          • MS Outlook
        • Developer Tools
          • Zendesk
          • ServiceNow
          • Jira
          • GitHub
          • Confluence
        • File Repositories
          • NetDocuments
          • AWS S3
          • Azure Blob
          • Google Drive
          • OneDrive
          • SharePoint
          • Viva Engage
          • Dropbox
          • Box
          • SMB
        • CRM
          • Hubspot
          • Salesforce
          • Automated Data Processing (ADP)
          • Marketo
          • Iterable
          • MS Dynamics 365 Sales
          • Salesforce Marketing Cloud
      • 🔔PlayBooks
        • What is LightBeam Playbooks?
        • Policy and Alerts
          • Types of Policies
          • How to create a rule set
            • File Extension Filter
          • Configuring Retention Policies
          • Viewing Alerts
          • Sub Alerts
            • Reassigning Sub-Alerts
            • Sub-alert States
          • Levels of Actions on Alerts
          • User Roles and Permissions
            • Admin View
            • Alert Owner View
            • Onboarding New Users
              • User Management
              • Okta Integration
              • Alert Assignment Settings
              • Email Notifications
            • Planned Enhancements
          • Audit Logs
          • No Scan List
          • Permit List
          • Policy in read-only mode
      • 📊Insights
        • Entity Workflow
        • Document Classification
        • Attribute Management Overview
          • Attributes Page View
          • Attribute Sets
          • Creating Custom Attribute
          • Attributes List
        • Template Builder
        • Label Management
          • MIP Integration
          • Google Labels Integration
      • 🗃️Reporting
        • Delta Reporting
        • Executive Report
        • LightBeam Lens
      • Scanning and Redaction of Files
        • On-demand scanning
      • How-to Guides
        • Leveraging LightBeam insights for structured data sources
      • LightBeam Dashboard Outlay
      • Risk Score
    • 🏛️PrivacyOps
      • Data Subject Request (DSR)
        • What is DSR?
        • Accessing the DSR Module
        • DSR Form Builder (DPO View)
          • Creating a New DSR Form
            • Using a Predefined Template
            • Creating a Custom Form
          • Form Configuration
          • Form Preview and Publishing
          • Multi-Form Management
          • Messaging Templates
        • Form Submission & Email Verification (Data Subject View)
        • DSR Management Dashboard (DPO View)
        • Processing DSR Requests
          • Data Protection Officer (DPO) Workflow
          • Self Service Workflow (Direct Validation)
          • Data Source Owner (DSO) Workflow
        • DSR Report
      • 🚧Consent Management
        • Overview
        • Consent Logs
        • Preference Centre
        • Settings
      • 🍪Cookie Consent
        • Dashboard
        • Banners
        • Domains
        • Settings
        • CMP Deployment Guide for Google Tag Manager
        • FAQs
      • 🔏Privacy Impact Assessment (PIA)
        • PIA Templates
        • PIA Assessment Workflow
        • Collaborator View
        • Process Owner Login View (With Collaborator)
        • Filling questionnaire without collaborator
        • Submitting the assessment for DPO review
        • DPO review process
        • Marking the assessment as reviewed
        • Editing and resubmitting assessments after DPO review
        • Revoke review request
        • Edit Reviewer
        • PIA Reports
      • ⏺️Records of Processing Activity (RoPA)
        • Creating a RoPA Template
          • How to clone a template
          • How to use a template
        • How to create a process
          • Adding Process Details
          • Adding Data Elements
          • Adding Data Subjects
          • Adding Data Retention
          • Adding Safeguards
          • Adding Transfers
          • Adding a Custom Section
          • Setting a Review Schedule
          • Data Flow Diagram
        • How to add a collaborator
        • Overview Section
        • Generating a RoPA Report Using LightBeam
        • Collaborator working on a ticket
    • 🛡️Governance
      • Access
        • Dashboard
        • Users
        • Groups
        • Objects
        • Active Directory Settings
        • Access Governance at a Data Source Level
        • Policies and Alerting
        • Access Governance Statistics
        • Governance Module Dashboard
      • Privacy At Partners
  • 📊Tools & Resources
    • 🔀API Documentation
      • API to Create Reports for Structured Datasource
    • ❓Onboarding Assessments
      • Structured Datasource Onboarding Questionnaire
        • MongoDB/CosmosDB Questionnaire
        • Oracle Datasource Questionnaire
      • SMB Questionnaire
    • 🛠️Administration
      • Audit Logs
      • SMTP
        • Basic and oAuth Configuration
      • User Management
        • SAML Identity Providers
          • Okta
            • LightBeam Okta SAML Configuration Guide
          • Azure
            • Azure AD SAML Configuration for LightBeam
          • Google
            • Google IDP
        • Local User Management
          • Adding a User to the LightBeam Dashboard
          • Reset Default Admin Password
  • 📚Support & Reference
    • 📅Release Notes
      • LightBeam v2.2.0
      • Reporting Release Notes
      • Q1 2024 Key Enhancements
      • Q2 2024 Key Enhancements
      • Q3 2024 Key Enhancements
      • Q4 2024 Key Enhancements
    • 📖Glossary
Powered by GitBook
  1. Tools & Resources
  2. Administration
  3. User Management
  4. SAML Identity Providers
  5. Azure

Azure AD SAML Configuration for LightBeam

PreviousAzureNextGoogle

Last updated 8 months ago

Configure Https for LightBeam endpoint before Azure AD SAML Configuration.

Azure AD Configuration

  1. Navigate to the Azure portal.

  2. Locate 'Enterprise applications' and select 'New Application'.

  3. Choose 'Create your own application' and name it appropriately.

  1. In the global search bar, type 'App registrations' and find your application by name.

  1. Select your application and click on 'Application ID URI'.

  1. Click on 'Add'.

5. Enter the Application ID URI. Click on 'Save'.

  1. Click on 'Overview' in the left navigation menu. Click on 'Endpoints'.

  2. Copy the URL from the 'Federation metadata document'.

Note: We need to use this URL to configure Azure AD as auth provider in LightBeam.

  1. Overview -> Managed application in the local directory (Click on app name)

  2. Next, we need to configure SAML and Assign users and groups.

Setup Single sign-on:

  • To configure SAML settings, click on Set up single sign on.

  • Click on SAML.

  • To configure basic SAML settings, select 'Edit' which will open a configuration window.

  • Identifier (Entity ID): <LIGHTBEAM_ENDPOINT>/auth/realms/master

  • Reply URL: <LIGHTBEAM_ENDPOINT>/auth/realms/master/broker/AzureAD/endpoint

Click on Save.

  • Now click on the Edit button to update user Attributes and Claims.

  • Click on Add a group claim.

  • After making the necessary changes, click 'Save'. The configured attributes and claims will then be displayed.

Add users and groups

  • Assign the necessary users and groups in Azure AD for integration.

  • Use the search functionality to find specific users or groups you want to assign. Select the users you want to integrate with the SAML application.

  • Assign the necessary roles and permissions for each user.

  • Add new users or groups as needed.

  • Ensure that each user or group has the appropriate level of access for the integration.

With the above steps Azure AD SAML configuration is done.

Configure Auth Provider

  • Now, the next step is to log in to LightBeam UI using admin user credentials and configure the Auth Provider.

Note: Before auth provider configuration we need to configure SMTP so role of the users can be changed.

  • Before Azure AD configuration, the login page looks like this:

  • Click on Auth Provider.

  • Select AzureAD from the drop-down list.

  • Select protocol as SAML

  • Provide the metadata URL copied above and click on Save.

  • After a successful Save message, click on Logout from the top right user profile icon.

  • On the login page, Azure AD option should now be visible.

Setting up default role

- Log in to Keycloak.

- Click on Roles.

- Click on Default Roles.

- In Client Roles, select LightBeam.

- Select lb-reader role from Available Roles and click on Add selected.

- With this default role for every user is set to lb-reader.

Configure Keycloak Mappers - Mappers

  • Log into your Keycloak instance and navigate to the 'Identity Providers' section.

  • Select 'AzureAD' from the list of identity providers, which will open a new page offering two tabs: 'Settings' and 'Mappers'.

It will open another page where we have 2 options Settings and Mappers.

We need to configure the following 4 different mappers

Scroll to the top of the page and click on 'Mappers', located next to the 'Settings' tab. Here, you'll create mappings for various user attributes.

  • Username Mapper:

    • For this Mapper, the Mapper Type will be “Username Template Importer” from the drop-down menu

    • The template will be ${ATTRIBUTE.http://schemas/xmlsoap.org/ws/2005/05/identity/claims/name}

  • Firstname Mapper:

    • For this Mapper, the Mapper Type will be “Attribute Importer” from the drop-down menu.

    • The Attribute Name will be the AD schema http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname

    • The User Attribute Name will be “firstName”.

  • Lastname Mapper:

    • For this Mapper, the Mapper Type will be “Attribute Importer” from the drop-down menu.

    • The Attribute Name will be the AD schema http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname

    • The User Attribute Name will be “lastName”.

  • Email mapper:

    • For this Mapper, the Mapper Type will be “Attribute Importer” from the drop-down menu.

    • The Attribute Name will be the AD schema http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

    • The User Attribute Name will be “email”.

Once all the mappers are configured it looks like the following:

Sign-in with AzureAD SSO from LightBeam login page.

Once you click on the Sign in with Azure AD option from the login page, it redirects to Microsoft and asks to select the user and provide credentials.

Once you have successfully logged in, the LightBeam Dashboard will be displayed. On the User Management screen, you will find a list of users along with their respective roles. By default, when a user is onboarded from Azure AD to the LightBeam system, they are assigned the "View Only" role. However, an admin can modify the "View Only" role to any other available role within the system.

As Azure AD users begin to log in to the LightBeam app, all the successfully logged-in users will be listed on the user management page.

Updating LightBeam in myapps.microsoft.com Portal


About LightBeam

LightBeam automates Privacy, Security, and AI Governance, so businesses can accelerate their growth in new markets. Leveraging generative AI, LightBeam has rapidly gained customers’ trust by pioneering a unique privacy-centric and automation-first approach to security. Unlike siloed solutions, LightBeam ties together sensitive data cataloging, control, and compliance across structured and unstructured data applications providing 360-visibility, redaction, self-service DSRs, and automated ROPA reporting ensuring ultimate protection against ransomware and accidental exposures while meeting data privacy obligations efficiently. LightBeam is on a mission to create a secure privacy-first world helping customers automate compliance against a patchwork of existing and emerging regulations.

Once the login is successful, click on the settings option from the top right () gearbox.

For any questions or suggestions, please get in touch with us at: .

📊
🛠️
⚙️
support@lightbeam.ai
Fig. 1 Azure AD SAML - Create your own application
Fig. 2. Azure AD SAML - App registrations
Fig. 3. Azure AD SAML - Application ID URI
Fig. 4. Azure AD SAML - Add Application ID URI
Fig. 5. Azure AD SAML - Save Application ID URI
Fig. 6. Azure AD SAML - Application ID URI
Fig. 7. Azure AD SAML - Set up single sign on
Fig. 8. Azure AD SAML - SAML
Fig. 9. Azure AD SAML - Basic SAML Configuration
Fig. 10. Azure AD SAML - Basic SAML Configuration - ID & Reply URL
Fig. 11. Azure AD SAML - Basic SAML Configuration - Attributes & Claims
Fig. 12. Azure AD SAML - Add a Group Claim
Fig. 13. Azure AD SAML - Add a Group Claim - Source attribute
Fig. 14. Azure AD SAML - Updated Attributes & Claims
Fig. 15. Azure AD SAML - Assign users & groups
Fig. 16. Azure AD SAML - Assign users & groups - Search for user
Fig. 17. Azure AD SAML - Assign users & groups - Assign user
Fig. 18. Azure AD SAML - Assign users & groups - Add user/group
Fig. 18.1 Azure AD SAML - Assign users & groups - Add user/group
Fig. 19 Azure AD SAML - Configure Auth Provider - Login Page
Fig. 19 Azure AD SAML - Configure Auth Provider - Select Auth Provider
Fig. 20 Azure AD SAML - Configure Auth Provider - New Login Page
Fig. 21 Azure AD SAML - Setting up default role - Click on Roles
Fig. 22 Azure AD SAML - Setting up default role - Click on Default Roles
Fig. 23 Azure AD SAML - Setting up default role - Client Roles
Fig. 24 Azure AD SAML - Setting up default role - Available Roles
Fig. 25 Azure AD SAML - Setting up default role - lightbeam
Fig. 26 Azure AD SAML - Keycloak Mappers - Identity Providers
AzureAD Mappers Configuration
LightBeam login page.
Fig. 32 Azure AD SAML - Sign in with Azure AD
Update the user details.
If the user exists select add to existing account.
Fig. 32 Azure AD SAML - User Management Screen
Add a site.
Provide LightBeam HTTPS FQDN