SAML Explained: How Enterprise SSO Works for API and Identity Engineers

·1 views

SAML (Security Assertion Markup Language) is an XML-based open standard that enables Single Sign-On (SSO), allowing users to authenticate once and access multiple applications without re-entering credentials. The protocol involves three core components: the user, an Identity Provider (IdP) such as Okta or Microsoft Entra ID, and a Service Provider like Salesforce or Workday. When a user attempts to access a service, the IdP authenticates them and issues a digitally signed XML document called a SAML Assertion, which the service provider validates to grant access. Crucially, the service provider never handles the user's password — only the identity provider does. Despite the rise of OAuth 2.0 and OpenID Connect, thousands of enterprise platforms including SAP, ServiceNow, and Oracle continue to rely heavily on SAML for centralized identity management.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Run a Local AI Coding Agent Using Ollama and Aider on Windows WSL2

A developer has documented a fully local AI coding setup using Ollama on Windows 11 and Aider inside Ubuntu running on WSL2, with no cloud services or dedicated GPU involved. The configuration uses Alibaba's Qwen2.5-Coder model, running in CPU-only mode on a machine with an Intel Core i7-1355U and 48 GiB of RAM. Ollama is kept on the Windows host to avoid duplicating model files, while Aider operates in the Linux environment where command-line development tools work more naturally. A key technical hurdle was enabling WSL2 mirrored networking so that Aider inside Ubuntu could communicate with the Ollama server exposed on Windows port 11434. The setup prioritizes keeping both source code and data entirely on the local machine, making it suitable for privacy-conscious developers without high-end AI hardware.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Common Python and VS Code Workspace Pitfalls and How to Fix Them

Developers using Python with VS Code often encounter environment issues that silently disrupt their workflow. One common problem is pip installing packages globally when the terminal fails to inherit the correct workspace context. Debugger conflicts can also arise when launch configuration files reference generic entry points instead of the active project module. Running multiple formatters like Black and Yapf simultaneously on save can cause clashes, while local environment variable files may be ignored by the built-in debugging terminal. Addressing these misconfigurations is key to restoring a stable and consistent development environment.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer launches 62 free browser tools that run locally with no uploads or sign-ups

A solo developer has built Tools Guru, a free website offering 62 utilities — including PDF editors, image tools, calculators, and developer utilities — that run entirely within the user's browser. No files are uploaded to any server, no account is required, and the site can be installed as an app and used offline. The project was motivated by frustration with ad-heavy websites that require file uploads and account creation for simple tasks. Standout features include an AI-powered background remover and an AI image generator, both of which process data locally using on-device neural network models. The site is live at toolsguru.shop, and the developer is actively seeking user feedback to identify bugs across the 62 tools.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Switching-Cost Anxiety: Why Your Tracker's Exit Policy Matters More Than Its Features

Choosing a project tracker involves more than evaluating current features — it's a long-term bet on whether the tool will survive funding changes, acquisitions, or pivots. Analysts tracked roughly 95 tool shutdowns and 101 acquisitions over an 18-month period, highlighting how quickly adopted software can disappear or transform. The real risk lies in data portability: if exporting your issues, comments, and history requires a support ticket or is locked behind a paid plan, the vendor effectively controls your exit. Experts suggest a simple 'leave test' before adopting any tracker — checking whether a full data export is instant and self-serve, available in open formats like JSON or CSV, and free from plan-tier restrictions. A tool that makes leaving effortless has priced its switching cost to near zero, which is itself a strong indicator of trustworthiness.

0 comments Read more at DEV Community