Identity & Single Sign-On

One secure sign-in across your apps with Azure AD, OAuth 2.0, OpenID Connect and Keycloak.

When every application has its own login, people juggle passwords and access is hard to control. We connect your applications to one identity provider so staff sign in once, roles decide what they can see, and access is removed in one place when someone leaves. We have implemented Azure AD single sign-on with role-based access for internal tools, and OpenID Connect based LTI 1.3 integrations for education platforms.

What we do

  • Single sign-on with Azure AD / Microsoft Entra ID
  • OAuth 2.0 and OpenID Connect integration
  • Keycloak set-up for your own identity server
  • Role-based access control
  • Access request and approval workflows
  • Standards-based integrations such as LTI 1.3

What you get

  • One login for staff across all tools
  • Access granted and removed in one place
  • Fewer password resets and support calls
  • Clear records of who can access what

Technologies

  • Azure AD
  • OAuth 2.0
  • OpenID Connect
  • Keycloak
  • JWT
  • LTI 1.3

Common questions

We use Microsoft 365. Can staff sign in with those accounts?

Yes. We connect your applications to Azure AD (Microsoft Entra ID) so staff use the account they already have.

Can different users see different things?

Yes. We map roles and groups from your identity provider to permissions in each application.

Do we need a paid identity product?

Not always. Keycloak is a free, open-source option we can host and configure for you.

Identity & Single Sign-On in practice

Projects where our team used this work in production.

Enterprise Security & Identity Management for SchoolCity

eSD Internal Tool - Azure AD SSO Integration

Implemented comprehensive Microsoft Azure Active Directory (AD) and Single Sign-On (SSO) solution for managing access requests across multiple internal applications based on predefined Azure groups and roles.

  • Microsoft Azure AD
  • Single Sign-On (SSO)
  • .NET Core
  • Vue.js

Education Technology for SchoolCity

LTI Integration (Tool Provider) In SchoolCity

Implemented LTI 1.3 tool provider with OIDC OpenID Connect authentication and LTI Advantage services for course management and faculty tools.

  • PHP
  • Vue.js
  • MySQL
  • Node.js

Education Technology for SchoolCity

LTI Integration (Tool Consumer) In IO Classroom

Implemented Learning Tools Interoperability (LTI) specification, upgrading from LTI 1.1 to LTI 1.3 with advanced features including deep linking, score saving, and JWKS token validation.

  • ASP.NET Core
  • C#
  • Microsoft SQL Server
  • .NET Core API
Chat on WhatsApp