Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Multi-Tenant Login Routing: Domain Discovery & Enforced SSO

The first enterprise customer's SSO works. Then the second one signs, then a tenth, and the login page becomes the problem. One email box and one password box no longer make sense. A user at acme.com should be sent to Acme's Okta. A user at globex.io should go to Microsoft Entra ID. A freelancer with a Gmail address invited into Acme's workspace should still be able to log in with a password, and…

This article discusses the implementation of multi-tenant login routing, specifically focusing on domain discovery and enforced SSO. The author, a Principal Software Engineer with extensive experience in building SaaS backends, explains how they tackled the challenge of routing users to the correct SSO provider based on their email domain.

The solution involves extracting the domain from the user's email address, looking it up in a table of verified domains mapped to tenant SSO connections, and redirecting the user accordingly. The article also covers security measures such as verifying domain ownership through a DNS TXT record and ensuring that the password or social login step is displayed when no matching domain is found.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Trap Streets for Code: How Mapmakers Caught Copiers, and How I Do It in Git

In the 1920s, two mapmakers at General Drafting, Otto G. Lindberg and Ernest Alpers, put a town on their map of New York that didn't exist.

  • Mapmakers used trap streets in 1920s to catch map copiers
  • TrapR tool uses markers, canaries, fingerprints to detect code copiers
  • Multi-layered approach helps monitor and protect code in Git repositories

Short Stints & Contract Hops: Framing a Choppy Timeline

The resume that worries people most in this series is not the one with a gap. It is the one with too many entries. Eight months at a startup that ran out of money.

  • Multiple short stints at startups and contracts create choppy timeline
  • Normalize dates using consistent format for ATS parsing
  • Group contract work under one umbrella entry with neutral reason

Kubelet readOnlyPort is an unauthenticated cluster inventory path

Kubelet readOnlyPort is an unauthenticated cluster inventory path The kubelet has a read-only port that serves requests with no authentication or authorization.

  • Kubelet's readOnlyPort is unauthenticated, exposing cluster inventory.
  • Default configuration lacks authentication, often overlooked.
  • Kubernetes advises disabling this port for enhanced security.

Upgrading Old PHP Versions Safely With Rector and CI

In almost every legacy PHP project Loop Origin takes on, the first question is the same: which PHP version is production on?

  • Identify current PHP version in production
  • Use tools PHPCompatibility, PHPStan, Rector for upgrade
  • Employ CI to run tests on both versions

Capacitor vs No-Code Wrappers: Shipping Your Web App to iOS and Android in 2026

You have a web app. Users keep asking for "the app". Rewriting everything in Swift and Kotlin is out of the question. So you wrap it.

  • Capacitor requires manual setup and native feature integration
  • No-code wrappers like Glideep provide quick, cost-effective app deployment
  • Both methods face app review challenges, requiring native navigation and offline screens

More from Saturday 21 November →