Docs/SSO Configuration/Azure AD (OIDC)

Azure AD (OIDC) Setup

Step-by-step guide to configure Single Sign-On with Microsoft Entra ID (Azure AD) using OpenID Connect.

Prerequisites

  • Azure AD tenant with admin access
  • SecureCodingHub org admin account
  • Organization domain verified in SecureCodingHub

Step 1 — Register an Application in Azure AD

1

Go to Azure PortalMicrosoft Entra IDApp registrationsNew registration

2

Name: SecureCodingHub SSO

3

Supported account types: Accounts in this organizational directory only

4

Redirect URI: Web → https://api.securecodinghub.com/api/sch/auth/sso/callback/oidc

5

Click Register

Step 2 — Create a Client Secret

1

Go to Certificates & secretsNew client secret

2

Description: SecureCodingHub

3

Expiry: Choose your policy (recommended: 24 months)

4

Copy the secret value immediately — it is shown only once

Step 3 — Note Your IDs

Collect the following values from your Azure AD application. You will need them in the next step.

SettingWhere to Find
Application (Client) IDOverview page
Directory (Tenant) IDOverview page
Client SecretCertificates & secrets
Discovery URLhttps://login.microsoftonline.com/{tenant-id}/v2.0/.well-known/openid-configuration

Step 4 — Configure SSO in SecureCodingHub

1

Log in as Org Admin → SSO Settings

2

Protocol: OIDC

3

Entity ID / Client ID: paste your Application ID

4

Discovery / Metadata URL: paste your OpenID configuration URL

5

Client Secret: paste the secret

6

Enable SSO

7

Click Save

app.securecodinghub.com/admin/sso
SSO Configuration
OIDC
a1b2c3d4-e5f6-7890-abcd-ef1234567890
https://login.microsoftonline.com/tenantid/v2.0/.well-known/openid-configuration
••••••••••••••••
Save

Step 5 — Test

1

Open an incognito/private browser window

2

Go to SecureCodingHub login

3

Enter an email address with your organization's domain

4

You should be redirected to Microsoft login

5

After authentication, you should be logged into SecureCodingHub

Security: Keep your Client Secret secure. If compromised, rotate it immediately in Azure Portal and update the value in SecureCodingHub.