Most businesses end up running several systems: a corporate website, a staff intranet, a CRM, a customer portal and perhaps a booking or learning platform. Asking people to remember a separate password for each one leads to reused passwords, forgotten-password requests and accounts that nobody switches off when a colleague leaves. Single sign-on (SSO) tackles this by letting one trusted sign-in open several systems. This guide explains the three standards behind most SSO projects, SAML, OAuth 2.0 and OpenID Connect, and how to plan an integration that is secure as well as convenient. For the user-experience side, see our earlier post on SSO and user experience.
What SSO Really Is
SSO is an experience rather than a single protocol. An identity provider (IdP), such as Microsoft Entra ID or Google Workspace, checks who the user is and applies your rules, including multi-factor authentication. Your website or web app then trusts the IdP's confirmation instead of keeping its own password list. The benefits are practical: fewer passwords to manage, one place to enforce MFA and one place to remove access when someone leaves. The risk is concentrated too, because the IdP becomes the key to everything, so its protection and the way each application checks its responses matter a great deal.
SAML, OAuth 2.0 and OpenID Connect in Plain Language
SAML 2.0, standardised in 2005, passes signed XML assertions through the browser and remains common in established enterprise and education environments. OAuth 2.0 (RFC 6749, 2012) is different: it is an authorisation framework that lets an application access specific resources without seeing the user's password. It was not designed to prove who someone is, and using it alone for login is a known implementation mistake. OpenID Connect (OIDC), published in 2014, closes that gap by adding a signed ID token on top of OAuth 2.0, and it runs behind a "Sign in with Google" button. As a rule of thumb, OIDC suits new web and mobile applications, SAML suits corporate systems or customers that require it, and OAuth 2.0 suits API access. Many organisations end up using more than one.
How ANGLIA Integrates SSO
SSO work sits naturally within our system development service. We begin by working with your IT contact to confirm which IdP you use, which protocol it supports and which users and roles the website or web app must recognise. We then integrate using established, maintained libraries and your IdP's own configuration instead of writing security code from scratch, and we map groups to roles so access follows your organisation chart. This often connects to other tools, which is where our experience with third-party API integration and CRM and payment connections helps.
Testing is where SSO projects are won or lost. On a staging environment we use test accounts to check normal sign-in, sign-out, expired sessions, removed users and wrong-audience responses, as well as the fallback administrator route. After launch we can monitor sign-in errors, track certificate and key renewals and keep the application patched, as covered in our post on ongoing support. We aim to make access simpler and safer, though the result still depends on how well your IdP itself is secured.
Considering SSO for an existing website or a new web app? Tell us which systems you want people to reach with one sign-in and which identity provider you use, via our contact page, and we will outline a sensible first phase.


