Naviga ID
Docs HomeInfomakerNaviga
  • Introduction
  • Release notes
  • Architecture
    • Authorization schema
  • Integrations
    • Customer Integration
      • Microsoft Azure
      • Google G Suite
      • Custom Identity Provider
      • Moving to a New Identity Provider
    • Service Integration
      • IMSG and headers
  • Services
    • Admin API
      • Routes
        • Health
        • Organizations
        • Permissions
        • Roles
        • Units
        • Services
        • Subjects
        • Organization applications
        • Internal applications
    • IMSG
      • Routes
        • Imsg-service
      • Environment variables
  • Shared modules
    • Http Test Server
      • HttpTestServer
    • Service Authorization Lib
      • Authorize
      • Errors
      • ExpressMiddleware
      • TokenUtils
      • Hapi plugin
      • ServiceAuthorizationError
      • AccessDenied
      • Unauthorized
      • ConfigError
  • Client Credentials
    • Managing Applications
    • Internal Naviga ID Docs
  • Access Token
    • Fetching and using Access Tokens
    • Validate Access Tokens
  • Local development
    • Local HTTPS support
  • Post Mortem
    • Broken backwards compatibility in access token service for client credentials, 20th Dec 2021
Powered by GitBook
On this page
  • Prerequisites
  • Information for Infomaker
  • Information for the integrating party
  • Allowed callback URLs
  • Allowed web origins

Was this helpful?

Export as PDF
  1. Integrations
  2. Customer Integration

Custom Identity Provider

This document describes how to integrate a custom Identity Provider using OpenID Connect with Naviga ID.

PreviousGoogle G SuiteNextMoving to a New Identity Provider

Last updated 5 years ago

Was this helpful?

Prerequisites

The party that wished to integrate with Naviga Login must have an identity provider compatible with the .

Specifically, the identity provider must support the OpenID Connect .

Information for Infomaker

Information we need to integrate your OIDC application:

  • URL to your (.well-known/openid-configuration)

  • Client ID

  • Client secret

Information for the integrating party

Allowed callback URLs

The following URLs must be added to the integrating party’s Whitelisted Callback URLs or equivalent:

Allowed web origins

The following URLs must be added to the integrating party’s Allowed Web Origins or equivalent:

OpenID Connect 1.0 Core specification
Authorization Code Flow
OpenID provider metadata file
http://localhost:9091/v1/org/{orgName}/login-callback
https://imas.imid.infomaker.io/v1/org/{orgName}/login-callback
https://imas.stage.imid.infomaker.io/v1/org/{orgName}/login-callback
http://localhost:9091
https://imas.imid.infomaker.io
https://imas.stage.imid.infomaker.io