Part 4 · IntelliCampus in OutSystems ODC
Connect IntelliCampus to Microsoft Entra SSO
Configure Microsoft Entra as an external OpenID Connect provider in OutSystems Developer Cloud, register the ODC callback URLs, and send unauthenticated IntelliCampus users to Microsoft sign-in.
Before you begin
Confirm the IntelliCampus Entra app is ready
Part 1 must already be complete for IntelliCampus. Keep the following values available while configuring ODC.
Entra Tenant ID
<organisation-tenant-guid>IntelliCampus Client ID
<intellicampus-client-guid>Client secret
Retrieve securely when neededPrimary domain
<tenant>.onmicrosoft.comWhy? ODC needs these values to discover Microsoft's sign-in endpoints and prove that IntelliCampus is the registered application.
Keep the secret private: enter it only in the protected ODC identity-provider configuration. Never place it in screenshots, source code, client actions, or documentation.
ODC Portal
1. Add an OpenID Connect provider
- Sign in to the ODC Portal.
- Open Management → Identity providers.
- Select Add provider.
- Choose OpenID Connect.
Why? OpenID Connect is the standard ODC uses to trust an external identity system such as Microsoft Entra ID.
Check: the OpenID Connect provider setup form is open.
Provider settings
2. Enter the Microsoft Entra configuration
Use the values below. Replace only the placeholders with your IntelliCampus Entra app information.
https://login.microsoftonline.com/<TenantID>/v2.0/.well-known/openid-configuration
After entering the discovery endpoint, select Get details. ODC should automatically load Microsoft's authorisation, token, and signing-key endpoints.
- Provider name
- Microsoft Entra IntelliCampus
- Discovery endpoint
- The tenant-specific URL shown above
- Client ID
- The IntelliCampus Application (client) ID from Entra
- Client secret
- The current IntelliCampus client secret from the secure store
- PKCE
- SHA-256
- Email verification
- Trust all emails as verified
- User profile mapping
- Username claim
preferred_username- Email claim
usernameas configured by the supplied ODC setup- Name claim
name- Photo URL claim
picture- Scopes
openid email profile
Why? The discovery endpoint tells ODC where Microsoft's login and token services are. Claims tell ODC which values from the Microsoft identity should become the ODC username, email, name, and profile photo. Scopes request only the basic identity information needed for login.
Validate the claims: claim availability can depend on the Entra token configuration and user type. Test with a real provisioned user and confirm that ODC receives the expected username and email before production rollout.
Check: select Save and confirm the provider appears in the ODC identity-provider list without a configuration error.
Callback URLs
3. Register ODC's authentication URLs in Entra
- In ODC, open the saved provider and copy its generated Login URL and Logout URL.
- Open Microsoft Entra ID → App registrations → IntelliCampus-SSO.
- Select Authentication → Add a platform → Web.
- Paste the ODC Login URL into Redirect URI.
- Paste the ODC Logout URL into Front-channel logout URL.
- Select Configure.
Why? Microsoft redirects users only to pre-approved URLs. Using the exact ODC-generated values prevents redirect mismatch errors and unsafe redirects.
Check: both URLs in Entra exactly match the ODC values, including HTTPS, path, letter case, and trailing slash.
Stage assignment
4. Assign the provider to the required ODC stages
- Return to the identity provider in ODC Portal.
- Select Assign.
- Select every stage that should use Entra SSO.
- Select Next, review the selection, and select Confirm.
Why? Creating a provider does not automatically activate it everywhere. Stage assignment controls whether Development, Test, and Production use the provider.
Safer rollout: validate Development first. Assign Test and Production only after login, access checks, and logout work correctly.
Check: the provider shows the expected assigned stages in ODC Portal.
ODC Studio
5. Redirect unauthenticated users to Microsoft
- Open the existing IntelliCampus application in ODC Studio.
- Open Common → OnException.
- Find the existing unauthenticated-user login destination.
- Remove that old login destination.
- Add the GetExternalLoginURL action for the configured provider.
- Redirect the browser to the external URL returned by that action.
Unauthenticated exception
GetExternalLoginURL
Redirect to Microsoft
Return to IntelliCampus
Why? This replaces the local login destination with the ODC-managed external-provider flow. ODC creates the correct state and callback information before sending the browser to Microsoft.
Keep the change focused: update only the unauthenticated login path. Do not redesign screens, expose the client secret, or replace existing product and role checks.
End-to-end flow
6. Understand the finished IntelliCampus login
User opens a protected IntelliCampus screen
↓
OnException requests the external login URL
↓
ODC redirects the browser to Microsoft Entra
↓
Microsoft authenticates the user
↓
Microsoft returns to the registered ODC Login URL
↓
ODC maps claims and creates the authenticated user context
↓
IntelliCampus applies its existing access rules and opens the requested screen
Why keep application access checks? Successful Microsoft authentication proves identity. IntelliCampus must still enforce tenant, active-user, product, and role permissions.
Testing checklist
7. Confirm Part 4 works
ODC loads details from the discovery endpoint
The provider saves without errors
ODC Login URL exactly matches the Entra redirect URI
ODC Logout URL exactly matches the Entra logout URL
The provider is assigned to the intended stage
Protected screens redirect to Microsoft
A provisioned user can sign in
Username, email, and name claims map correctly
Unauthorised users remain blocked
The requested screen opens after login
Logout ends the ODC and Microsoft sign-in flow
No secret appears in browser code or logs