Working with SSO?

SAML or OIDC login not working? We fix it.

Single sign-on fails in small, specific ways: one attribute named wrong, a certificate that rotated last week, a redirect URI that does not match by one character. We read the actual assertion and the actual error, then make them agree.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

auth.log

still failing

What it is

Single sign-on (OAuth, SAML) at a glance

Single sign-on lets users log in once and reach multiple applications without entering a password at each one. The two dominant protocols are SAML 2.0, an XML-based standard that has run enterprise B2B federation since 2005, and OpenID Connect, a JSON layer on top of OAuth 2.0 that now carries most consumer and modern business logins.

SCIM 2.0 handles the user and group provisioning side, so accounts appear and disappear in the application as the identity provider changes them. The identity providers people actually run include Okta, Microsoft Entra ID, Google Workspace, Auth0, OneLogin, JumpCloud, Ping Identity and the self-hosted Keycloak. Hawkins.Tech works on both sides of an SSO integration: the application that accepts the login and the enterprise customer configuring their directory.

Type
Identity standards and integration
SAML 2.0 standard
OASIS, ratified in 2005
OIDC standard
OpenID Foundation, finalised in 2014
License
Open standards, free to implement
Typically used for
B2B SaaS app logins, workforce SSO, customer identity federation, zero-trust access

The honest version

Single sign-on (OAuth, SAML) pros and cons

No technology is all upside. This is where Single sign-on (OAuth, SAML) earns its place and where it tends to cause trouble.

Where Single sign-on (OAuth, SAML) is strong

  • One login, many appsUsers sign in once at the identity provider and reach every connected application without a second password prompt.
  • Central user lifecycleSCIM pushes new hires, role changes and leavers from the directory into each application automatically, so accounts stay in sync.
  • Stronger auth in one placeMFA, device checks and conditional access live at the IdP level in Okta, Entra ID, JumpCloud or Google, and every connected app inherits them.
  • Offboarding that actually worksDisable a leaver in the directory and access drops everywhere at once, instead of hoping somebody remembered each tool.
  • One audit trailLogin events and access decisions concentrate at the IdP, which makes compliance work for SOC 2, ISO 27001 and HIPAA much easier to evidence.

Where Single sign-on (OAuth, SAML) bites

  • SAML signing is finickyXML signatures break on whitespace changes, on certificate rotation, and on the shift from SHA-1 to SHA-256. One wrong byte invalidates the whole assertion.
  • Attribute mapping is the usual bugThe identity provider sends one claim name, the application expects another, and the login either fails or creates a stranger. This is the single most common integration problem.
  • OIDC details get half doneNonce, state and PKCE all have a job in the flow, and skipping any one of them leaves a real security hole. Refresh token rotation is a separate project most teams underestimate.
  • SCIM varies by IdPThe spec is one thing and each identity provider implements a slightly different slice of it, so provisioning that works against Okta often stumbles against Entra ID.
  • The SSO taxMany SaaS vendors still charge extra for SAML, which turns a basic security control into a line item that finance has to approve.
  • The IdP is a single point of failureWhen the identity provider has an outage, every connected application loses logins at the same moment, so the blast radius is wider than people expect.

Sound familiar?

Common Single sign-on (OAuth, SAML) problems we fix

The Single sign-on (OAuth, SAML) problems that bring people to us, and what you have once each one is fixed.

signature validation failed

SAML assertions are being rejected

Usually a rotated signing certificate, a mismatched entity ID, or XML canonicalisation that the two sides disagree on. The browser trace tells you which.

Assertions verified and accepted

attribute 'email' not found

SAML attribute mapping is wrong

The IdP is sending http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress and the app wants email. Users log in and land as the wrong person or get a 500.

Claims mapped to the app's schema

redirect_uri mismatch

OIDC login redirects fail

The registered callback URL does not match exactly, often a trailing slash or http versus https. OIDC is strict on purpose here.

Redirects allowed and verified

no refresh_token returned

Users get logged out every hour

The offline_access scope was never requested, or the IdP policy does not grant it, so the app has no way to extend the session.

Refresh flow working end to end

SCIM PATCH 400

SCIM provisioning stopped working

The IdP pushes an operation the app does not understand, commonly a group membership change with a path the server rejects. Users stop appearing or stop being deactivated.

Users and groups sync again

User has no assigned role

Entra ID users cannot sign in

The enterprise application exists but the user or their group has not been assigned to it, so Entra ID refuses the token request before the app ever sees it.

Assignments and roles in order

clock skew exceeded

Logins fail intermittently

Server time has drifted beyond the five-minute window the assertion allows, usually on a VM without NTP. The failure looks random until you check the clocks.

Time synced, drift alerted on

legacy LDAP, no MFA

You need to add SSO to an older app

An in-house or legacy application still uses its own user table and nobody wants to leave it that way before the next audit.

SAML and OIDC in front of it

What we do

SSO help, from one broken login to full rollout

Call us for one failing assertion, or hand us the whole identity project.

Rescue
Logins failing right now across Okta, Entra ID or Google. We read the real assertion and the real error, then make them agree.
SSO for your SaaS
Add SAML and OIDC to your product so enterprise customers can connect their own IdP without a bespoke project each time.
SCIM provisioning
User and group sync from Okta, Entra ID, JumpCloud or Google, tested against each one rather than just the spec.
Auth migrations
Moving from legacy LDAP or in-house user tables onto SAML and OIDC, with a cutover plan that does not strand anyone.
Security review
PKCE, nonce, state, token lifetimes, certificate rotation and refresh handling checked against what the standards actually require.
Managed Tech
Ongoing care of your identity stack: certificate renewals, IdP upgrades, SCIM drift and a team to call.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Single sign-on (OAuth, SAML) alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Single sign-on (OAuth, SAML) questions

Something else? Call+1 737 727 7327

Can you set up SAML SSO for our SaaS product so our enterprise customers can use Okta, Entra ID or Google?

Yes. We add a SAML service provider to your application, build the per-customer configuration, and test the flow end to end against each major identity provider. You get a setup guide your customers can follow, and we stay on call for the first few customer rollouts so edge cases get handled quickly.

Why are our users getting 'NameID' or 'attribute' errors after SAML login?

Almost always an attribute mapping mismatch. The identity provider is sending a claim with one name or format, and the application is looking for a different one. We read the real SAML response from the browser, compare it against what the app expects, and align the mapping on whichever side is easier to change.

Can you add OIDC login, meaning Sign in with Google, Microsoft or Apple, to our app?

Yes. We register the OAuth client, wire up the authorization code flow with PKCE, handle nonce and state correctly, and link the resulting identity to your existing user records. If you also want to accept enterprise SSO through the same path we can set that up alongside.

How do we set up SCIM provisioning so users and groups sync from the IdP?

We implement the SCIM 2.0 endpoints your identity provider expects, test them against Okta, Entra ID and whichever others you need, and work through the small differences in how each IdP interprets the standard. Then we set up alerting so a provisioning failure is noticed on the day it happens.

Can you migrate us from legacy auth such as LDAP or in-house users to SAML plus OIDC?

Yes, and the important part is the plan. We keep both paths working during cutover, map existing accounts into the new identity provider by email or employee ID, and give you a rollback route in case something unexpected shows up in production.

How much does SSO work cost?

Estimates are free. Describe the application and which identity providers you need to support, and you get a price before any work begins.

Free estimate

SSO giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.