Logilica Documentation
HomepageDemoBlogContact
  • About Logilica
    • Overview
  • Getting Started
    • Onboarding Data
    • Onboarding Users
    • Setting up Teams
  • Integration
    • Connecting Tools
    • Uploading Custom Data
  • Metrics & Reports
    • Introduction
      • Navigation
      • Dashboards
      • Data Exploration
    • Epics Delivery Tracker
    • Planning
      • Ticket Lead Time
      • Ticket Velocity
      • Ticket Overload
      • Sprint Health
      • Ticket Activities / Risks
    • Code
      • Code Cycle Time
      • Coding Velocity
      • Review Process
      • Developer Health
      • Code Activities / Risks
    • Build
    • Team Management
      • Teams Overview
      • Team Pulse
      • Activity Lens
    • Reports
    • Customization
    • Glossary
  • Configuration
    • User Management
    • Managing Contributors
    • Menu Management
    • Release Detection
    • Targets & Thresholds
    • DORA Configuration
  • Advanced
    • API Token Management
    • Import API
      • API Overview
      • Uploading Planning Data
      • Uploading CI Build Data
        • CDEvents Integration
      • Uploading Test Data
      • Uploading Team Data (beta)
      • Repositories
      • Uploading Contributors Data
    • Export API
    • DataStudio
      • Data Models
        • CI Build
        • CI Build Stage
        • Contributor
        • Coverage Commit
        • Coverage File
        • Coverage Label
        • Coverage Test Result
        • Jira Component
        • Jira Epic
        • Jira Hierarchy Issues
        • Jira Issue Hierarchy Link
        • Jira Issue
        • Jira Issue
        • Jira Label
        • Jira Project
        • Jira Release
        • Jira Sprint
        • Project
        • Pull Request
        • Pull Request
        • Release
        • Team
      • Advanced Transformations
    • Integrations: Data Mapping
      • GitHub Projects Support
  • SSO Integration
    • Keycloak SSO
    • Microsoft Entra SSO
  • Subprocessors
  • Changelog
Powered by GitBook
On this page
  1. SSO Integration

Microsoft Entra SSO

Set up Logilica with Microsoft Entra's Single Sign-On

PreviousKeycloak SSONextSubprocessors

Last updated 3 days ago

Microsoft Entra is a cloud-based Identity Management service that implements an Identity Provider (IdP), using protocols such as SAML. Logilica's SSO supports Microsoft Entra's SAML SSO.

To enable Microsoft Entra SAML SSO with Logilica, please complete the following:

In Microsoft Entra, navigate to the Applications Single Sign-On settings page via Home > Enterprise applications > SAML-based Sign On.

Please ensure the application is set up with SAML-based single sign-on.

  1. Match Client ID and Entity ID In the Logilica SSO configuration, ensure the Entity ID field has the same value as Microsoft Entra's Identifier (Entity ID) field.

  1. Set Reply URL (Assertion Consumer Service URL) In Microsoft Entra, set the Reply URL to https://logilica.io/api/user/saml/callback?domain=<domain-name>.

If you want to test service provider-initiated SSO in Microsoft Entra, set the Sign On URL to 'https://logilica.io/login'. This is an optional field.

  1. Fill in the Entry URL and Certificate fields The Entry URL and Certificate field can be obtained from the Application's SAML Certificates > Federation Metadata XML document. The Entry URL should be in the format: https://login.microsoftonline.com/<tenant-id>/saml2

Please ensure you have at least one active user in the Application with a verified email.

With this, Microsoft Entra's SAML SSO has been set up with Logilica. For further details on logging in with SSO, please navigate to the page.

SSO Integration
Microsoft Entra SSO Entity ID Settings
Logilica Organisation Single Sign On settings
Microsoft Entra SSO Reply URL Settings
Microsoft Entra SAML 2.0 Identity Provider Metadata
Logilica Organisation Single Sign On settings