SSONorvia SSO Guide
Part 3 · IntelliBroadcast login

Connect IntelliBroadcast to Microsoft Entra SSO

Replace IntelliBroadcast's existing login entry point with Microsoft Entra sign-in while keeping its current tenant checks, product roles, screens, and business features unchanged.

Simple objective

What changes in Part 3?

Microsoft Entra will check the user's login and password. IntelliBroadcast will then use the returned Entra identity to find the matching Norvia user and confirm that the user may access IntelliBroadcast.

Why are both systems involved? Entra performs authentication—proving who the person is. IntelliBroadcast performs authorisation—checking whether that person, tenant, and product role are active.
Security warning: the source document contains credential-like example values. This page intentionally uses placeholders. If any value in the document is real, revoke and replace that secret before continuing.
Entra configuration

1. Register the login and logout URLs

  1. Open portal.azure.com → Microsoft Entra ID → App registrations.
  2. Open the IntelliBroadcast app registration.
  3. Select Authentication → Add a platform → Web.
  4. Add the login redirect URI and front-channel logout URL shown below.
  5. Select Configure, then confirm both URLs appear under the Web platform.
Login redirect URI:
https://<your-intellibroadcast-host>/signin-oidc

Front-channel logout URL:
https://<your-intellibroadcast-host>/signout-callback-oidc
Why? Entra redirects the browser only to URLs that were registered in advance. The value must use HTTPS and exactly match the application's public host and callback path.
Check: both URLs are visible in the IntelliBroadcast app registration and contain no spaces or trailing slash differences.
Configuration inventory

2. Confirm the application values

Record these values securely. Add the tenant ID, client ID, and secret reference to the IntelliBroadcast product in Norvia Backoffice.

ApplicationIntelliBroadcast
Tenant ID<organisation-tenant-guid>
Client ID<intellibroadcast-client-guid>
Client secretStored securely — never paste here
Login callback/signin-oidc
Logout callback/signout-callback-oidc
Why? IntelliBroadcast loads its Entra configuration from the product record. The secret reference tells the app which protected App Service setting contains the actual secret.
Login flow

3. Understand what happens when a user signs in

User opens IntelliBroadcast
↓
The app redirects to Microsoft Entra
↓
Entra checks the login email and password
↓
Entra returns validated tid and oid claims
↓
IntelliBroadcast finds ExternalIdentityMapping
↓
The app checks the user, tenant, and IntelliBroadcast role
↓
If allowed, create the application session and open the requested page
Why use tid and oid? tid identifies the Entra tenant and oid identifies the Entra account. Email addresses can change, so email must not be the primary identity lookup.
App Service

4. Store the client secret securely

Open Azure Portal → App Services → IntelliBroadcast → Settings → Environment variables. Add the setting whose name is stored in NorviaProducts.SSOAppSecretReference.

Setting name: IntelliBroadcastSSOSecret
Setting value: <actual-client-secret>
Why? The database stores only the setting name. The actual secret stays in protected App Service configuration and is resolved by the server at startup.
Application settings

5. Add non-secret IntelliBroadcast settings

{
  "ProductHash": "<existing-intellibroadcast-product-hash>",
  "AppBaseUrl": "https://<your-intellibroadcast-host>",
  "SSO": {
    "CallbackPath": "/signin-oidc",
    "SignedOutCallbackPath": "/signout-callback-oidc"
  }
}
Why? ProductHash finds the correct Norvia product row. AppBaseUrl creates the exact public callback URLs. The callback paths are handled by OpenID Connect middleware, so separate callback controllers are not needed.
Implementation requirements

6. Replace only login, session integration, and logout

AreaRequired behaviourWhy
StartupUse ProductHash to load product ID, tenant ID, client ID, and secret reference. Resolve the secret from configuration. Configure OpenID Connect authorization-code flow and cookies.Keeps product identity and secrets centrally configured.
LoginIf no valid local session exists, automatically challenge Entra. Let middleware handle /signin-oidc.Removes the old password entry point and gives users one Microsoft login.
User lookupUse validated tid and oid to find ExternalIdentityMapping, then load the Norvia user.Object IDs remain stable even if an email address changes.
AuthorisationConfirm the user is active, the tenant is active, and an IntelliBroadcast product role exists before creating a session.Successful Microsoft login alone does not grant product access.
Return URLAfter approval, create the existing application session and return to the originally requested local page.Users continue where they intended without allowing unsafe external redirects.
LogoutClear the local session, start Entra sign-out, handle /signout-callback-oidc, and land on a public page without immediately challenging again.Both the local app and Microsoft session must end cleanly.
Scope protection

7. Keep the change focused

Change

  • Authentication configuration
  • Login challenge
  • Identity-to-user lookup
  • Existing session integration
  • Logout flow

Do not change

  • Database schema or migrations
  • Business screens or functionality
  • Tenant isolation or role rules
  • Microsoft Graph provisioning
  • Existing product features
  • Credentials in source code
Why? Part 2 already creates users and mappings. Part 3 only consumes that identity information to sign users into IntelliBroadcast.
Testing

8. Confirm Part 3 works

Unauthenticated pages redirect to Entra
Login callback URL exactly matches Entra
tid and oid find the mapped Norvia user
Inactive users are denied
Inactive tenants are denied
Users without an IntelliBroadcast role are denied
Authorised users return to the requested page
No custom login form remains
Logout clears both sessions
Logout does not immediately sign in again
No credentials appear in code or logs
Existing screens and tenant filtering still work

← Return to the SSO overview