# Single sign-on (SSO)

Single sign-on (SSO) is an authentication method that lets users access multiple applications and websites with one set of login credentials, using identity providers and authentication standards.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## CVE-2026-54039 - LibreChat: Pre-registration account takeover via attacker-controlled \`provider\` field and social-login email fallback

DevFeed: [CVE-2026-54039 - LibreChat: Pre-registration account takeover via attacker-controlled \`provider\` field and social-login email fallback](<https://devfeed.tech/articles/cve-2026-54039-librechat-pre-registration-account-takeover-via-attacker-controlled-provider-field-and-social-login-email-fallback-146635.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-54039>)

Author: CVEFEED.io; github.com

Published: 2026-11-20T20:17:42Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [conditional](<https://devfeed.tech/tags/conditional.md>), [created](<https://devfeed.tech/tags/created.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-54039](<https://devfeed.tech/tags/cve-2026-54039.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [data](<https://devfeed.tech/tags/data.md>), [email](<https://devfeed.tech/tags/email.md>), [fallback](<https://devfeed.tech/tags/fallback.md>), [field](<https://devfeed.tech/tags/field.md>), [librechat](<https://devfeed.tech/tags/librechat.md>), [librechat-ai](<https://devfeed.tech/tags/librechat-ai.md>), [login](<https://devfeed.tech/tags/login.md>), [published](<https://devfeed.tech/tags/published.md>), [social](<https://devfeed.tech/tags/social.md>)

### AI overview

LibreChat versions 0.7.0 through 0.8.5 are vulnerable when local registration is enabled and at least one social provider is configured. Registration can persist an attacker-supplied provider value for a known victim email. On the victim's social sign-in, an email-fallback path accepts the record by provider name without checking the provider subject identifier, binding the victim's OAuth session and attacker's password session to the same account. This gives the attacker persistent read and write access to the victim's data. A first-user administrator role is a conditional additional impact on fresh deployments. The issue is fixed in version 0.8.6.

### Source excerpt

CVE ID :CVE-2026-54039 Published : Nov. 20, 2026, 8:17 p.m. | 37 minutes ago Description :LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. From 0.7.0 until 0.8.6, when local registration is enabled and at least one social provider is configured, POST /api/auth/register passes an unparsed request object into api/server/services/AuthService.js, allowing an unauthenticated attacker to persist a forged provider value for a known victim email. The api/strategies/socialLogin.js email-fallback path then accepts the planted record when the victim signs in because it compares the stored provider name without requiring the provider subject identifier. The victim OAuth session and the attacker local-password session become bound to the same user record, giving the attacker persistent read and write access to data created by the victim. The first-user administrator role is an additional conditional impact only on a fresh deployment. This issue is fixed in version 0.8.6. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Use Kimi Code CLI with models on Amazon Bedrock

DevFeed: [Use Kimi Code CLI with models on Amazon Bedrock](<https://devfeed.tech/articles/use-kimi-code-cli-with-models-on-amazon-bedrock-144615.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/use-kimi-code-cli-with-models-on-amazon-bedrock/>)

Author: Alex Thewsey

Published: 2026-11-20T00:33:30Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [configure](<https://devfeed.tech/tags/configure.md>), [connect](<https://devfeed.tech/tags/connect.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [kimi](<https://devfeed.tech/tags/kimi.md>), [models](<https://devfeed.tech/tags/models.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [request](<https://devfeed.tech/tags/request.md>), [send](<https://devfeed.tech/tags/send.md>), [separate](<https://devfeed.tech/tags/separate.md>), [sso](<https://devfeed.tech/tags/sso.md>), [standard](<https://devfeed.tech/tags/standard.md>), [using](<https://devfeed.tech/tags/using.md>)

### AI overview

Kimi Code CLI v2.7.0 adds a native Amazon Bedrock provider that uses the standard AWS credential chain, including named profiles and SSO, reducing the need to manage a separate Bedrock API key. The provider resolves AWS credentials, generates and renews a short-lived bearer token, builds a regional endpoint, and routes requests to a model or inference profile. Setup requires CLI and AWS CLI versions, model access, suitable IAM permissions, and an explicit Region in Kimi Code configuration; a Region set only in the AWS profile is insufficient. Model capabilities should be declared and checked against the model card. Global inference may offer broader availability and lower pricing, but configured Region remains the source Region. The desktop and web "connected" status does not verify credentials, permissions, model access, or connectivity, so the post recommends testing with an actual request. Explicit API keys take precedence when configured, and users remain responsible for protecting AWS credentials and scoping permissions.

### Source excerpt

Kimi Code CLI v2.7.0 adds a native Amazon Bedrock provider, so you can connect the open source coding agent to models like Kimi K3.1 Pro using your standard AWS credential chain (named profiles or SSO) instead of a separate API key. This post shows how to configure the provider and send your first request.

## Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT

DevFeed: [Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT](<https://devfeed.tech/articles/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt-144197.md>)

Original publisher: [Read original article](<https://www.securityweek.com/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt/>)

Author: Eduard Kovacs

Published: 2026-11-19T19:21:06Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [bug](<https://devfeed.tech/topics/bug.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [apt](<https://devfeed.tech/tags/apt.md>), [armory-castle](<https://devfeed.tech/tags/armory-castle.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [backdoors](<https://devfeed.tech/tags/backdoors.md>), [beyondtrust](<https://devfeed.tech/tags/beyondtrust.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [bug](<https://devfeed.tech/tags/bug.md>), [china](<https://devfeed.tech/tags/china.md>), [china-apt](<https://devfeed.tech/tags/china-apt.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [critical](<https://devfeed.tech/tags/critical.md>), [espionage](<https://devfeed.tech/tags/espionage.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [featured](<https://devfeed.tech/tags/featured.md>), [google](<https://devfeed.tech/tags/google.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patched](<https://devfeed.tech/tags/patched.md>), [vcenter](<https://devfeed.tech/tags/vcenter.md>), [vcenter-server](<https://devfeed.tech/tags/vcenter-server.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [vmware-vcenter](<https://devfeed.tech/tags/vmware-vcenter.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [warp-panda](<https://devfeed.tech/tags/warp-panda.md>), [zero-day](<https://devfeed.tech/tags/zero-day.md>)

### AI overview

Google says the China-linked group Armory Castle exploited CVE-2026-123890 in VMware vCenter for more than two months before Broadcom patched it. The unauthenticated flaw could grant administrator access. Mandiant says the attackers first entered through a BeyondTrust Remote Support zero-day, then used the custom tool Bonesaw to steal vCenter's LMDB and SAML signing material, create an SSO administrator account, deploy backdoors, and access an ESXi host. Broadcom fixed the flaw in vCenter 9.1.1.0200, 9.0.2.0200, and 8.0 U3m; no public patch is available for version 7.0, which is out of general support. Mandiant recommends applying patches and checking systems for compromise.

### Source excerpt

Google says a China-linked espionage group exploited a critical VMware vCenter authentication bypass before Broadcom released a patch. The post Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT appeared first on SecurityWeek.

## Step-up authentication: how to right-size authentication to risk

DevFeed: [Step-up authentication: how to right-size authentication to risk](<https://devfeed.tech/articles/step-up-authentication-how-to-right-size-authentication-to-risk-142070.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/step-up-authentication-how-to-right-size-authentication-to-risk/>)

Author: Abrom Douglas

Published: 2026-11-18T23:49:07Z

Content type: article

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [MFA](<https://devfeed.tech/topics/mfa.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [account-balance](<https://devfeed.tech/tags/account-balance.md>), [acr](<https://devfeed.tech/tags/acr.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [amr](<https://devfeed.tech/tags/amr.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [balance](<https://devfeed.tech/tags/balance.md>), [banking](<https://devfeed.tech/tags/banking.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [identity](<https://devfeed.tech/tags/identity.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [risk](<https://devfeed.tech/tags/risk.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [step-up-authentication](<https://devfeed.tech/tags/step-up-authentication.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [user](<https://devfeed.tech/tags/user.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Amazon Cognito step-up authentication lets applications match authentication strength and freshness to the risk of an action. The app requests a target level with OIDC `acr_values` and optional `max_age`, or `TARGET_ACR_VALUES` and `MAX_AGE` in the `USER_AUTH` API flow. Cognito reports the achieved level and factors in `acr` and `amr`; `auth_time` tracks interactive authentication, while token refresh preserves assurance and does not reset freshness. The application remains responsible for choosing required levels, validating returned claims, and enforcing access. Four patterns cover transaction-level checks, differing requirements across apps sharing SSO, API or SDK sign-in, and federated OIDC providers that map external assurance values. Step-up requires the Essentials or Plus plan; on lower tiers, API requests raise `FeatureUnavailableInTierException`, while managed login ignores `acr_values` and proceeds with normal authentication.

### Source excerpt

Not every action a user takes in an application carries the same risk. Viewing an account balance in a banking application isn't the same as wiring several thousand dollars to a new payee. In practice, though, many applications ask users to prove their identity once at sign-in and then treat every action the same from [...]

## How AUMOVIO centralized AI access with Databricks Unity Gateway

DevFeed: [How AUMOVIO centralized AI access with Databricks Unity Gateway](<https://devfeed.tech/articles/how-aumovio-centralized-ai-access-with-databricks-unity-gateway-140784.md>)

Original publisher: [Read original article](<https://www.databricks.com/blog/how-aumovio-centralized-ai-access-databricks-unity-gateway>)

Author: Louis Rottmeier; Maximilian Fest; Michael Boesl; Michael Weber; Martin Gindler; Kelly Albano

Published: 2026-11-18T14:03:54Z

Content type: article

Language: en

Sources: [Databricks](<https://devfeed.tech/sources/databricks.md>)

Topics: [databricks](<https://devfeed.tech/topics/databricks.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [internal developer platform](<https://devfeed.tech/topics/internal-developer-platform.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-coding](<https://devfeed.tech/tags/agentic-coding.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-application](<https://devfeed.tech/tags/ai-application.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-cost](<https://devfeed.tech/tags/ai-cost.md>), [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [ai-platform](<https://devfeed.tech/tags/ai-platform.md>), [ai-spending](<https://devfeed.tech/tags/ai-spending.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [industries](<https://devfeed.tech/tags/industries.md>), [language](<https://devfeed.tech/tags/language.md>), [manufacturing](<https://devfeed.tech/tags/manufacturing.md>), [unity-gateway](<https://devfeed.tech/tags/unity-gateway.md>)

### AI overview

AUMOVIO centralized LLM access through Databricks Unity Gateway after separate provider integrations and use case gateways became harder to operate, attribute costs to, and govern consistently. Because its 1ADP data platform already runs on Databricks and uses Microsoft Entra ID, applications can exchange corporate identity tokens for access without separate accounts or distributed API keys. Curated 1adp-* aliases route to approved models across Databricks, Google Vertex AI, Azure OpenAI, AWS Bedrock and others; changing a provider or model does not require consumer code changes. Terraform manages endpoints, routing, fallback order, rate limits and guardrails. Central approvals, policies and usage tracking support governance; payload logging is off by default and requires explicit approved justification. AUMOVIO joins token usage with project or personal cost center assignments for dashboards and chargeback, and maintains its own curated catalog and employee AI app. Teams still test their chosen models, and AUMOVIO remains responsible for architecture, security and application quality. Its next phase is shared agents and managed or bring-your-own MCP connections, raising questions--

### Source excerpt

As AI adoption grew, AUMOVIO teams developed different ways to access large language...

## Use Windows Hello or Apple Touch ID to log into Bitwarden

DevFeed: [Use Windows Hello or Apple Touch ID to log into Bitwarden](<https://devfeed.tech/articles/use-windows-hello-or-apple-touch-id-to-log-into-bitwarden-144656.md>)

Original publisher: [Read original article](<https://bitwarden.com/blog/use-windows-hello-or-apple-touch-id-to-log-into-bitwarden/>)

Published: 2026-11-18T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Bitwarden Blog](<https://devfeed.tech/sources/the-bitwarden-blog.md>)

Topics: [Windows](<https://devfeed.tech/topics/windows.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [account](<https://devfeed.tech/tags/account.md>), [apple](<https://devfeed.tech/tags/apple.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bitwarden](<https://devfeed.tech/tags/bitwarden.md>), [computer](<https://devfeed.tech/tags/computer.md>), [easily](<https://devfeed.tech/tags/easily.md>), [id](<https://devfeed.tech/tags/id.md>), [it](<https://devfeed.tech/tags/it.md>), [log](<https://devfeed.tech/tags/log.md>), [option](<https://devfeed.tech/tags/option.md>), [passkey](<https://devfeed.tech/tags/passkey.md>), [passkeys](<https://devfeed.tech/tags/passkeys.md>), [password](<https://devfeed.tech/tags/password.md>), [password-manager](<https://devfeed.tech/tags/password-manager.md>), [passwordless](<https://devfeed.tech/tags/passwordless.md>), [product-updates](<https://devfeed.tech/tags/product-updates.md>), [security-tips](<https://devfeed.tech/tags/security-tips.md>), [store](<https://devfeed.tech/tags/store.md>), [touch-id](<https://devfeed.tech/tags/touch-id.md>), [vault](<https://devfeed.tech/tags/vault.md>), [windows](<https://devfeed.tech/tags/windows.md>), [windows-hello](<https://devfeed.tech/tags/windows-hello.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Bitwarden lets users log in to its web app or extension and unlock the vault with a passkey stored on their computer, using Windows Hello or Apple Touch ID for verification and decryption. To set it up, create a login passkey in Settings > Security > Master password > Log in with passkey, save it to the device, and enable "Use for vault encryption." Later, choose "Log in with passkey" and complete the operating system prompt. The passkey is bound to the computer; the article says this flow avoids entering a username or master password and bypasses two-step login. Requirements include a Bitwarden account with a master password, SSO with master password as the only supported SSO type, the organization's "Require single sign-on (SSO)" policy turned off, a supported device with Hello or Touch ID configured, and a Chromium-based browser (Chrome, Edge, Brave, or Vivaldi).

### Source excerpt

Easily get into your vault with Windows Hello or Apple Touch ID, thanks to the Log in with passkey option! Store a passkey on your computer and use it for secure authentication and decryption - without a password!

## Agent identity for Amazon WorkSpaces for AI agents

DevFeed: [Agent identity for Amazon WorkSpaces for AI agents](<https://devfeed.tech/articles/agent-identity-for-amazon-workspaces-for-ai-agents-138612.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/desktop-and-application-streaming/agent-identity-for-amazon-workspaces-for-ai-agents/>)

Author: Roberto Moreno

Published: 2026-11-17T20:05:28Z

Content type: article

Language: en

Sources: [Desktop and Application Streaming](<https://devfeed.tech/sources/desktop-and-application-streaming.md>)

Topics: [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Entra ID](<https://devfeed.tech/topics/entra-id.md>), [okta](<https://devfeed.tech/topics/okta.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-workspaces](<https://devfeed.tech/tags/amazon-workspaces.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [aws-end-user-computing](<https://devfeed.tech/tags/aws-end-user-computing.md>), [can](<https://devfeed.tech/tags/can.md>), [end-user-computing](<https://devfeed.tech/tags/end-user-computing.md>), [first](<https://devfeed.tech/tags/first.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [generation](<https://devfeed.tech/tags/generation.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [leave](<https://devfeed.tech/tags/leave.md>), [management](<https://devfeed.tech/tags/management.md>), [model](<https://devfeed.tech/tags/model.md>), [non-human-identities](<https://devfeed.tech/tags/non-human-identities.md>), [people](<https://devfeed.tech/tags/people.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [re-invent](<https://devfeed.tech/tags/re-invent.md>), [workspaces](<https://devfeed.tech/tags/workspaces.md>)

### AI overview

Amazon WorkSpaces for AI agents uses on-behalf-of (OBO) identity so an agent acts with a user's delegated access while remaining separately identifiable. The user signs in through an existing identity provider (such as Microsoft Entra ID or Okta); the agent exchanges that sign-in for a provider-signed token naming both identities. AWS STS issues short-lived credentials for the agent's IAM role, and IAM policies can restrict which agents act for which users and environments. CloudTrail records both identities, with per-action data events available when enabled. Revoking an agent or user prevents new sessions; stopping an active agent requires removing role permissions or revoking active role sessions. Non-domain-joined fleets use the basic flow. Domain-joined fleets additionally require working certificate-based authentication and Active Directory user attributes in the token; users must be synchronized from Active Directory. The model depends on a signed-in user and does not fit agents operating without one. IdP token attribute mapping is security-critical, and long-running work needs token refresh under the IdP's policies.

### Source excerpt

Identity management has always followed whoever, or whatever, does the work. The first generation secured people: authenticate a person, authorize what they can reach, and remove their access when they leave. The second generation extended that model to software through service accounts, which are non-human identities with a fixed set of permissions and, often, long-lived [...]

## GitHub Copilot CLI adds Microsoft Entra sign-in as a preview

DevFeed: [GitHub Copilot CLI adds Microsoft Entra sign-in as a preview](<https://devfeed.tech/articles/github-copilot-cli-adds-microsoft-entra-sign-in-as-a-preview-139397.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-17-github-copilot-cli-adds-microsoft-entra-sign-in-as-a-preview>)

Author: Allison

Published: 2026-11-17T18:00:35Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [GitHub Copilot CLI](<https://devfeed.tech/topics/github-copilot-cli.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [billing](<https://devfeed.tech/tags/billing.md>), [business](<https://devfeed.tech/tags/business.md>), [cli](<https://devfeed.tech/tags/cli.md>), [client-apps](<https://devfeed.tech/tags/client-apps.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [github-copilot-cli](<https://devfeed.tech/tags/github-copilot-cli.md>), [github-enterprise](<https://devfeed.tech/tags/github-enterprise.md>), [managed](<https://devfeed.tech/tags/managed.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-entra](<https://devfeed.tech/tags/microsoft-entra.md>), [preview](<https://devfeed.tech/tags/preview.md>), [release](<https://devfeed.tech/tags/release.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

GitHub Copilot CLI adds Microsoft Entra sign-in in public preview, requiring CLI version 1.0.113 or later; Entra authentication is currently supported on Windows and macOS, with Linux support to follow. For enterprises using OIDC with Enterprise Managed Users, silent SSO accesses a linked GitHub account without a separate GitHub sign-in. It requires an assigned Copilot Business or Enterprise license and the organization's Copilot CLI policy; requests use GitHub inference and are governed by the GitHub Copilot plan. This SSO option is limited to CLI and VS Code. For Frontier organizations with a Microsoft 365 Copilot license and usage-based billing, sign-in can provide terminal access to Microsoft Copilot models without a GitHub account. That path uses Microsoft 365 inference, with model access and limits managed in Microsoft 365 Copilot settings. Work IQ MCP can provide Microsoft 365 work data as context. The excerpt says setup steps are in the CLI documentation.

### Source excerpt

GitHub Copilot CLI now supports Microsoft Entra authentication in public preview. You can sign in with your Microsoft Entra account to silently authenticate to a linked GitHub Enterprise Managed User... The post GitHub Copilot CLI adds Microsoft Entra sign-in as a preview appeared first on The GitHub Blog.

## Announcing account switching: one browser, many accounts

DevFeed: [Announcing account switching: one browser, many accounts](<https://devfeed.tech/articles/announcing-account-switching-one-browser-many-accounts-138162.md>)

Original publisher: [Read original article](<https://appwrite.io/blog/post/announcing-account-switching>)

Author: Aditya Oberai

Published: 2026-11-17T00:00:00Z

Content type: release

Language: en

Sources: [Appwrite Blog](<https://devfeed.tech/sources/appwrite-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [browser](<https://devfeed.tech/topics/browser.md>), [account](<https://devfeed.tech/topics/account.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [admin](<https://devfeed.tech/tags/admin.md>), [after](<https://devfeed.tech/tags/after.md>), [agencies](<https://devfeed.tech/tags/agencies.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [auth](<https://devfeed.tech/tags/auth.md>), [browser](<https://devfeed.tech/tags/browser.md>), [call](<https://devfeed.tech/tags/call.md>), [can](<https://devfeed.tech/tags/can.md>), [one](<https://devfeed.tech/tags/one.md>), [switch](<https://devfeed.tech/tags/switch.md>), [switching](<https://devfeed.tech/tags/switching.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Appwrite Auth account switching lets one browser or app install hold sessions for several accounts while keeping one active. Call `createDevice` at startup; sign-ins then join that device, and an account picker can use `getDevice` and `updateDeviceSession` to switch accounts. Appwrite manages session and device secrets in cookies, so existing authenticated requests continue to use the active account without extra parameters. `deleteSession` signs out only the active account; `deleteDevice` signs out all accounts. Switching is enabled by default and can be disabled per project. Sessions still count toward project limits, and a switch issues a fresh session secret, invalidating other copies of that session. The feature is live on Appwrite Cloud and is slated for the next self-hosted release.

### Source excerpt

Appwrite Auth now supports account switching, so users can stay signed in to several accounts in one browser or app and switch between them in one call.

## Building a Secure MCP (Model Context Protocol) Server with Auth0

DevFeed: [Building a Secure MCP (Model Context Protocol) Server with Auth0](<https://devfeed.tech/articles/building-a-secure-mcp-model-context-protocol-server-with-auth0-136615.md>)

Original publisher: [Read original article](<https://auth0.com/blog/building-secure-mcp-server-with-auth0/>)

Author: Kevin Kimani

Published: 2026-11-16T17:06:00Z

Content type: tutorial

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [Auth0](<https://devfeed.tech/topics/auth0.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Remote Procedure Call (RPC)](<https://devfeed.tech/topics/rpc.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [context](<https://devfeed.tech/tags/context.md>), [data](<https://devfeed.tech/tags/data.md>), [go](<https://devfeed.tech/tags/go.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [learn](<https://devfeed.tech/tags/learn.md>), [learn-how-to](<https://devfeed.tech/tags/learn-how-to.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model](<https://devfeed.tech/tags/model.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [server](<https://devfeed.tech/tags/server.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The guide builds a Go MCP server that uses Auth0 Authorization Code with PKCE to issue user-linked access tokens, then validates JWT signatures, issuer, audience, and expiry against Auth0 JWKS. Auth0 RBAC supplies department permissions; the server authorizes from the token's requested-and-approved `scope` claim, mapping `read:engineering` or `read:hr` to a department. It registers only that department's resources for each session and returns "resource not found" for cross-department reads to reduce information leakage. Missing or invalid tokens receive 401 with OAuth resource metadata; valid tokens without a required scope receive 403. The walkthrough also configures OAuth Protected Resource Metadata and demonstrates requests with cURL. It distinguishes Client Credentials as suitable for automated machine-to-machine pipelines, while choosing Authorization Code for deployments governed by a real user. Production follow-ups include token refresh, client-secret rotation, richer audit logging, and finer-grained authorization for more complex access patterns.

### Source excerpt

Learn how to build an MCP server in Go and secure it with Auth0 using OAuth 2.1, PKCE, and RBAC-backed scopes, so AI agents only see the data their user is authorized to access.

## Microsoft's Outage Shows the Cost of One Vendor Running Everything

DevFeed: [Microsoft's Outage Shows the Cost of One Vendor Running Everything](<https://devfeed.tech/articles/microsoft-s-outage-shows-the-cost-of-one-vendor-running-everything-136462.md>)

Original publisher: [Read original article](<https://feed.itsfoss.com/link/24361/17525729/microsofts-outage-reaction>)

Author: Abhishek Prakash

Published: 2026-11-16T16:22:00Z

Content type: news

Language: en

Sources: [It's FOSS](<https://devfeed.tech/sources/it-s-foss.md>)

Topics: [microsoft 365](<https://devfeed.tech/topics/microsoft-365.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [air-gapped](<https://devfeed.tech/tags/air-gapped.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [attack](<https://devfeed.tech/tags/attack.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [backup](<https://devfeed.tech/tags/backup.md>), [big-tech](<https://devfeed.tech/tags/big-tech.md>), [browser](<https://devfeed.tech/tags/browser.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [collaboration-suite](<https://devfeed.tech/tags/collaboration-suite.md>), [communications](<https://devfeed.tech/tags/communications.md>), [company](<https://devfeed.tech/tags/company.md>), [email](<https://devfeed.tech/tags/email.md>), [global](<https://devfeed.tech/tags/global.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [news](<https://devfeed.tech/tags/news.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [outage](<https://devfeed.tech/tags/outage.md>)

### AI overview

Microsoft's November outage disrupted Outlook and dependent services across many countries; Microsoft attributed it preliminarily to an earlier network capacity upgrade interacting with a later network change, and said it was not a cyberattack. The article's central finding is that failures can affect any provider, but concentration lets one fault disrupt many organizations at once. It describes shared authentication as a particular weak point and argues that sovereignty depends on choice and operational control, not only data location. Suggested steps include mapping single-vendor dependencies, prioritizing critical services, piloting migrations after auditing integrations and user habits, and rehearsing a minimal fallback. Open standards and self-hostable open source software may make it easier to switch or maintain services independently, but open source does not prevent outages, and moving clouds can replace one dependency with another. The article notes that a 500-person Exchange migration could take several months; mailboxes are easier to move than accumulated integrations, permissions and habits.

### Source excerpt

After Microsoft's global email outage, open source rivals say the real problem is putting everything in one basket.

## Hello Again: Exploiting Replay Protected Monotonic Counters to Brute-Force Windows Hello PINs

DevFeed: [Hello Again: Exploiting Replay Protected Monotonic Counters to Brute-Force Windows Hello PINs](<https://devfeed.tech/articles/hello-again-exploiting-replay-protected-monotonic-counters-to-brute-force-windows-hello-pins-136044.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.18126>)

Author: Christian Werling, Matti Finder, Hans Niklas Jacob, Julian Prein, Niclas K\\"uhnapfel, Jean-Pierre Seifert

Published: 2026-11-16T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [bitlocker](<https://devfeed.tech/topics/bitlocker.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [amd](<https://devfeed.tech/tags/amd.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bitlocker](<https://devfeed.tech/tags/bitlocker.md>), [brute-force](<https://devfeed.tech/tags/brute-force.md>), [brute-force-attacks](<https://devfeed.tech/tags/brute-force-attacks.md>), [bus](<https://devfeed.tech/tags/bus.md>), [chip](<https://devfeed.tech/tags/chip.md>), [controller](<https://devfeed.tech/tags/controller.md>), [cost](<https://devfeed.tech/tags/cost.md>), [counter](<https://devfeed.tech/tags/counter.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [days](<https://devfeed.tech/tags/days.md>), [desktops](<https://devfeed.tech/tags/desktops.md>), [device](<https://devfeed.tech/tags/device.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [windows](<https://devfeed.tech/tags/windows.md>), [windows-hello](<https://devfeed.tech/tags/windows-hello.md>)

### AI overview

The abstract reports that flaws in RPMC-based rollback protection can let an attacker restore fTPM lockout state and bypass PIN anti-hammering. With low-cost interposer hardware, researchers found that voltage glitching can expose Winbond SPI flash's HMAC key, enabling counter forgery, and that AMD's NV controller fails to verify RPMC increments. On two AMD desktops without RPMC flash, reflashing an older image also reset fTPM lockout counters. The demonstrated attack recovered a four-digit Windows Hello PIN in 40 hours rather than 69 days; the same primitive reduced the worst-case time for a default six-digit BitLocker TPM+PIN protector from 19 years to 20 days. The abstract says a compromised Hello PIN can also expose device-bound keys and Hello-based enterprise SSO.

### Source excerpt

arXiv:2611.18126v1 Announce Type: new Abstract: Windows Hello is the primary authentication mechanism on over one billion Windows 11 devices, supporting PINs as short as four digits. Such low-entropy PINs are viable only because the TPM's anti-hammering protection mitigates brute-force attacks. Most modern x86 platforms rely on firmware TPMs (fTPMs) that persist their non-volatile (NV) state, including the lockout state, to SPI flash. On newer platforms, rollback prevention of this state is delegated to the flash chip via Replay Protected Monotonic Counters (RPMCs), a JEDEC-standardized mechanism operating over a physically accessible bus. We present the first practical security analysis of RPMC in shipping x86 systems. Using low-cost interposer hardware, we identify multiple implementation flaws, two of which fundamentally undermine RPMC's security model: First, Winbond SPI flash - the leading NOR flash vendor with over 25% market share - leaks its HMAC key under voltage glitching, enabling arbitrary counter forgery. Second, AMD's NV controller does not verify RPMC increments, so an interposer can suppress them unnoticed. Moreover, AMD platforms without RPMC flash appear to lack NV rollback protection altogether: on two AMD desktops, reflashing an old image resets the fTPM's lockout counters. Both flaws enable rollbacks of the fTPM's NV state (AMD, Intel, or Pluton), including its lockout counters. We demonstrate this end-to-end on locked, encrypted hardware: our setup finds a 4-digit Windows Hello PIN in 40 hours instead of 69 days. A compromised PIN also grants access to device-bound keys and Hello-based enterprise SSO. The same primitive defeats BitLocker's TPM+PIN pre-boot protector, reducing the worst-case time for a default-length 6-digit PIN from 19 years to 20 days.

## What Are EMA, ID-JAG, and XAA? Scoped Access for AI Agents

DevFeed: [What Are EMA, ID-JAG, and XAA? Scoped Access for AI Agents](<https://devfeed.tech/articles/what-are-ema-id-jag-and-xaa-scoped-access-for-ai-agents-133476.md>)

Original publisher: [Read original article](<https://www.cyera.com/blog/ema-id-jag-xaa-token-exchange>)

Author: Barak Shelef

Published: 2026-11-13T18:05:32Z

Content type: article

Language: en

Sources: [Cyera Blogs](<https://devfeed.tech/sources/cyera-blogs.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [acquisition](<https://devfeed.tech/tags/acquisition.md>), [actions](<https://devfeed.tech/tags/actions.md>), [admin](<https://devfeed.tech/tags/admin.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [adversarial](<https://devfeed.tech/tags/adversarial.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [cyera](<https://devfeed.tech/tags/cyera.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [id](<https://devfeed.tech/tags/id.md>), [identity](<https://devfeed.tech/tags/identity.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [policy](<https://devfeed.tech/tags/policy.md>), [token](<https://devfeed.tech/tags/token.md>), [token-exchange](<https://devfeed.tech/tags/token-exchange.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

The article argues that AI agents need task-scoped, short-lived credentials instead of broad, long-lived OAuth grants: narrow instructions alone cannot bound what an agent may do. XAA is the cross-application brokering pattern, ID-JAG is an active IETF draft for short-lived, audience-bound identity assertions, and EMA is the stable MCP extension applying that approach. Token Exchange narrows credentials at each boundary. Cyera Identity AAM evaluates an agent's intent against policy before requesting a token; on approval, it brokers scoped access and records the decision. Adoption depends on both the identity provider and each MCP server, and support and scope granularity vary. The article advises verifying current vendor support and asking about production availability, per-resource scope enforcement, and EMA delivery dates. Where EMA is unavailable, AAM says it can use other server-supported mechanisms, but recommends validating that behavior in each environment.

### Source excerpt

Cyera Identity's Agentic Access Management supports EMA, ID-JAG, XAA, and OAuth Token Exchange, giving AI agents scoped, policy-evaluated access that expires when the task ends.

## This Week In Security: Four-Digit Patch Tuesday, SSH Exploited, GitBook Breach, Android GhostMap

DevFeed: [This Week In Security: Four-Digit Patch Tuesday, SSH Exploited, GitBook Breach, Android GhostMap](<https://devfeed.tech/articles/this-week-in-security-four-digit-patch-tuesday-ssh-exploited-gitbook-breach-android-ghostmap-132374.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/11/13/this-week-in-security-four-digit-patch-tuesday-ssh-exploited-gitbook-breach-android-ghostmap/>)

Author: Mike Kershaw

Published: 2026-11-13T15:00:26Z

Content type: news

Language: en

Sources: [Hackaday](<https://devfeed.tech/sources/hackaday.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [OpenSSH](<https://devfeed.tech/topics/openssh.md>), [ssh](<https://devfeed.tech/topics/ssh.md>), [Android Security](<https://devfeed.tech/topics/android-security.md>), [Android](<https://devfeed.tech/topics/android.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [active-directory](<https://devfeed.tech/tags/active-directory.md>), [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [adb](<https://devfeed.tech/tags/adb.md>), [adobe](<https://devfeed.tech/tags/adobe.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [alpine](<https://devfeed.tech/tags/alpine.md>), [android](<https://devfeed.tech/tags/android.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [breach](<https://devfeed.tech/tags/breach.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [ghostmap](<https://devfeed.tech/tags/ghostmap.md>), [gitbook](<https://devfeed.tech/tags/gitbook.md>), [hackaday-columns](<https://devfeed.tech/tags/hackaday-columns.md>), [krebs](<https://devfeed.tech/tags/krebs.md>), [linux](<https://devfeed.tech/tags/linux.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-patch-tuesday](<https://devfeed.tech/tags/microsoft-patch-tuesday.md>), [openssh](<https://devfeed.tech/tags/openssh.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patch-tuesday](<https://devfeed.tech/tags/patch-tuesday.md>), [ransomware](<https://devfeed.tech/tags/ransomware.md>), [security](<https://devfeed.tech/tags/security.md>), [security-hacks](<https://devfeed.tech/tags/security-hacks.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [this-week-in-security](<https://devfeed.tech/tags/this-week-in-security.md>)

### AI overview

The roundup reports a broad patch surge and several active security concerns. OpenSSH's password bypass on affected musl-based systems is being exploited; Alpine users with Internet-reachable SSH should update or disable password authentication, while Debian, Ubuntu, SUSE, Red Hat, CentOS and stock OpenWrt are reported unaffected. After a GitBook SSO flaw led to infrastructure access, GitBook treated all customer data as exposed; customers should rotate API and integration secrets and review repository activity by the GitBook app. Bitdefender describes an Android 10+ crash loop from a malformed APK that can require a factory reset; Google passed the report to a feature team rather than treating it as a security issue. The text also notes MPTCP-related kernel fixes across Ubuntu and Red Hat releases, while stressing the flaw is not specific to MPTCP and has no confirmed in-the-wild exploitation. Firefox fingerprinting changes reportedly reduced unique identification from 75% to 46% in one measured script. These are selected stories from the supplied roundup, not comprehensive coverage of every issue.

### Source excerpt

It's the second Tuesday of the month, and that means another Microsoft Patch Tuesday. The new normal is that the numbers are hard to believe. Brian Krebs reports that this ...read more

## Convex Auth v2 is finally here

DevFeed: [Convex Auth v2 is finally here](<https://devfeed.tech/articles/convex-auth-v2-is-finally-here-132657.md>)

Original publisher: [Read original article](<https://stack.convex.dev/convex-auth-v2>)

Author: Stack

Published: 2026-11-12T18:00:00Z

Content type: release

Language: en

Sources: [Stack](<https://devfeed.tech/sources/stack.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [version](<https://devfeed.tech/topics/version.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [backend](<https://devfeed.tech/tags/backend.md>), [beta](<https://devfeed.tech/tags/beta.md>), [better-auth](<https://devfeed.tech/tags/better-auth.md>), [components](<https://devfeed.tech/tags/components.md>), [convex](<https://devfeed.tech/tags/convex.md>), [keys](<https://devfeed.tech/tags/keys.md>), [notes](<https://devfeed.tech/tags/notes.md>), [releases](<https://devfeed.tech/tags/releases.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [sign-up](<https://devfeed.tech/tags/sign-up.md>), [table](<https://devfeed.tech/tags/table.md>), [transaction](<https://devfeed.tech/tags/transaction.md>), [users](<https://devfeed.tech/tags/users.md>), [v2](<https://devfeed.tech/tags/v2.md>)

### AI overview

Convex Auth v2 is presented as the recommended starting point for new Convex apps: authentication runs in the Convex backend through separate components for the core system and each sign-in method, with passwords, passkeys and common social logins. The author's notes app example shows separate accounts seeing only their own notes. Password data stays in the password component as hashes that application code cannot read; token keys no longer need manual generation. Sign-up creates a user in the app's own schema in the same transaction, and reactive session data makes sign-out propagate across tabs. The excerpt says v2 currently lacks multi-factor authentication, email magic links and one-time codes, and supports React and Next.js only. Existing v1 apps have no migration tooling yet, though v1 continues to receive security updates; the author points to Clerk and WorkOS for enterprise features such as SSO.

### Source excerpt

Convex Auth v2 is out, and it's the proper, official, non-beta version of auth for Convex. I had my agent add it to a little notes app, then dug into how it works: components for each sign-in method, no keys to generate, your own users table and sign-up in one transaction. Plus which auth option I'd pick for a Convex app right now.

## Announcing Vipps MobilePay login for Appwrite Auth

DevFeed: [Announcing Vipps MobilePay login for Appwrite Auth](<https://devfeed.tech/articles/announcing-vipps-mobilepay-login-for-appwrite-auth-130992.md>)

Original publisher: [Read original article](<https://appwrite.io/blog/post/announcing-vipps-mobilepay-login>)

Author: Aditya Oberai

Published: 2026-11-11T00:00:00Z

Content type: release

Language: en

Sources: [Appwrite Blog](<https://devfeed.tech/sources/appwrite-blog.md>)

Topics: [Why Rely on a Social Auth Library?](<https://devfeed.tech/topics/why-rely-on-a-social-auth-library.md>), [Appwrite](<https://devfeed.tech/topics/appwrite.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [auth](<https://devfeed.tech/tags/auth.md>), [denmark](<https://devfeed.tech/tags/denmark.md>), [finland](<https://devfeed.tech/tags/finland.md>), [login](<https://devfeed.tech/tags/login.md>), [norway](<https://devfeed.tech/tags/norway.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [sweden](<https://devfeed.tech/tags/sweden.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Appwrite Auth adds Vipps MobilePay as one OAuth2 provider for users in Norway and Sweden (Vipps) and Denmark and Finland (MobilePay), with a separate sandbox provider for test accounts. Configure each provider with the matching sales unit's keys and register its exact redirect URI; add the app domain as a web platform. Client apps can use `createOAuth2Session`; server-rendered apps can use `createOAuth2Token` and must validate the returned `state` before exchanging the user ID and secret for a session. Appwrite requests `openid`, `name`, and `email`, and marks email verified only when the provider confirms it. Additional scopes can request fields such as phone number or address, which must be read from the userinfo endpoint. Login has no refresh tokens, so provider API access may require signing in again after token expiry, though the Appwrite session is unaffected. Users must be at least 15. The providers are available on Appwrite Cloud and are slated for the next self-hosted release.

### Source excerpt

Appwrite Auth now supports Vipps MobilePay as an OAuth2 provider, so users in Norway, Denmark, Finland, and Sweden can sign in with the app they pay with.

## What CIAM Teams Can Learn from the DHS Data Breach

DevFeed: [What CIAM Teams Can Learn from the DHS Data Breach](<https://devfeed.tech/articles/what-ciam-teams-can-learn-from-the-dhs-data-breach-134056.md>)

Original publisher: [Read original article](<https://fusionauth.io/blog/dhs-data-breach>)

Author: Andrew Hatfield

Published: 2026-11-11T00:00:00Z

Content type: article

Language: en

Sources: [FusionAuth](<https://devfeed.tech/sources/fusionauth-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Data Management](<https://devfeed.tech/topics/data-management.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [breach](<https://devfeed.tech/tags/breach.md>), [ciam](<https://devfeed.tech/tags/ciam.md>), [customer-data](<https://devfeed.tech/tags/customer-data.md>), [data-breach](<https://devfeed.tech/tags/data-breach.md>), [dhs](<https://devfeed.tech/tags/dhs.md>), [education](<https://devfeed.tech/tags/education.md>), [multi-tenant](<https://devfeed.tech/tags/multi-tenant.md>), [security](<https://devfeed.tech/tags/security.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

The DHS breach exposed data about more than 40,000 employees and contractors, but the reported access method remains unverified. Its CIAM lessons focus on limiting what a valid login can do: enforce server-side permissions for every action and resource, minimize exposure of identity metadata in APIs and tokens, validate tenant membership and resource ownership on each request, and test whether compromised sessions and tokens can be revoked promptly. The article also recommends monitoring post-login activity--such as bulk retrieval, enumeration, and privilege changes--and linking API events to users, sessions, and tenants. It notes that ending an identity-provider session may not end application sessions, and revoking refresh tokens may leave issued access tokens usable until expiration. Sender-constrained tokens such as DPoP can reduce reuse of stolen tokens, while shorter lifetimes and stronger controls involve usability tradeoffs. A checklist covers authorization, identity-data exposure, tenant isolation, session and token handling, and incident response.

### Source excerpt

Explore 5 SSO security lessons for CIAM teams in the wake of the DHS data breach, plus a practical checklist to help protect customer data.

## SSO sign-in consent screen: What it is and how to handle denials

DevFeed: [SSO sign-in consent screen: What it is and how to handle denials](<https://devfeed.tech/articles/sso-sign-in-consent-screen-what-it-is-and-how-to-handle-denials-127144.md>)

Original publisher: [Read original article](<https://workos.com/blog/sso-sign-in-consent-screen>)

Author: WorkOS

Published: 2026-11-10T16:15:34Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Exception handling](<https://devfeed.tech/topics/exception-handling.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>)

Tags: [branding](<https://devfeed.tech/tags/branding.md>), [callback](<https://devfeed.tech/tags/callback.md>), [consent](<https://devfeed.tech/tags/consent.md>), [sso](<https://devfeed.tech/tags/sso.md>)

### AI overview

WorkOS's SSO consent screen appears after identity-provider authentication and before the app receives an authorization code, showing the returned email and provider origin for user confirmation. Approval is remembered per user; the screen is enabled by default in new environments, while older ones should be checked in Authentication settings. Handle `signin_consent_denied` before expecting a code: direct the user to contact their admin and support about a possible phishing attempt, and keep this distinct from `access_denied`. For IdP-initiated logins, consent appears until approval; a configured sign-in endpoint can route the login into a standard SP-initiated flow and includes `connection_id`. Review the applicable environment branding, colors, and logos, since sandbox branding does not predict production. The screen adds a deliberate user check alongside other defenses, but cannot verify the displayed identity for the user.

### Source excerpt

The sign-in consent screen shows users their email and identity provider before SSO completes. When it appears, how to handle a denial, and what to brand.

## One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration

DevFeed: [One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration](<https://devfeed.tech/articles/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration-127002.md>)

Original publisher: [Read original article](<https://www.techrepublic.com/article/one-identity-unveils-active-roles-8-6-with-enhanced-security-and-administration/>)

Author: CyberNewsWire

Published: 2026-11-10T15:38:31Z

Content type: release

Language: en

Sources: [TechRepublic](<https://devfeed.tech/sources/techrepublic.md>)

Topics: [active directory](<https://devfeed.tech/topics/active-directory.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Entra ID](<https://devfeed.tech/topics/entra-id.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [active-directory](<https://devfeed.tech/tags/active-directory.md>), [administration](<https://devfeed.tech/tags/administration.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [identity](<https://devfeed.tech/tags/identity.md>), [press-release](<https://devfeed.tech/tags/press-release.md>), [roles](<https://devfeed.tech/tags/roles.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Active Roles 8.6 fixes an RSTS configuration security issue and includes the features, enhancements and resolved issues from versions 8.3-8.5, superseding those releases. One Identity describes the update as a cumulative administrator and integration upgrade, not a visual redesign. The release line adds a REST API and Redistributable Secure Token Server capabilities for API access and SAML 2.0 federated authentication. The product also offers a configurable thick-client UI modeled on the familiar Active Directory experience, a console spanning Active Directory, Microsoft Entra ID and Microsoft 365, and PowerShell and VBScript support. The supplied text does not detail individual API changes or compare 8.6 with other products.

### Source excerpt

One Identity has introduced Active Roles 8.6, strengthening secure and streamlined Active Directory administration with cumulative platform improvements, expanded API capabilities and greater authentication flexibility. The post One Identity Unveils Active Roles 8.6 with Enhanced Security and Administration appeared first on TechRepublic.

## CVE-2026-76877 - WPML Multilingual CMS \<= 4.9.7 - Unauthenticated Authentication Bypass in Language-per-Domain SSO via 'wpml\_sso\_token\_domain' Parameter

DevFeed: [CVE-2026-76877 - WPML Multilingual CMS \<= 4.9.7 - Unauthenticated Authentication Bypass in Language-per-Domain SSO via 'wpml\_sso\_token\_domain' Parameter](<https://devfeed.tech/articles/cve-2026-76877-wpml-multilingual-cms-4-9-7-unauthenticated-authentication-bypass-in-language-per-domain-sso-via-wpml-sso-token-domain-parameter-124925.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-76877>)

Author: CVEFEED.io; wordfence.com

Published: 2026-11-10T06:47:00Z

Content type: article

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [race-condition](<https://devfeed.tech/topics/race-condition.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [WordPress](<https://devfeed.tech/topics/wordpress.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [browser](<https://devfeed.tech/tags/browser.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [can](<https://devfeed.tech/tags/can.md>), [client](<https://devfeed.tech/tags/client.md>), [cms](<https://devfeed.tech/tags/cms.md>), [condition](<https://devfeed.tech/tags/condition.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-76877](<https://devfeed.tech/tags/cve-2026-76877.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [details](<https://devfeed.tech/tags/details.md>), [domain](<https://devfeed.tech/tags/domain.md>), [language](<https://devfeed.tech/tags/language.md>), [parameter](<https://devfeed.tech/tags/parameter.md>), [sso](<https://devfeed.tech/tags/sso.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

WPML Multilingual CMS versions up to and including 4.9.7 have an unauthenticated authentication bypass in language-per-domain SSO during logout. On the logout landing page, the SSO nonce is generated after authentication cookies are discarded, making it a shared anonymous nonce for the current 12-hour tick; the associated transient maps it to the user without binding it to the sign-out action or requesting client. An attacker can derive the nonce and, within the 60-second SSO timeout, submit a forged `wpml_sso_token_domain` with `wpml_user_signed_in` to a secondary language domain before the logout iframe completes. WordPress may then issue authentication cookies for the victim, including an administrator, but only while that user is actively logging out during the race window. The source rates severity 8.1 (HIGH).

### Source excerpt

CVE ID :CVE-2026-76877 Published : Nov. 10, 2026, 6:47 a.m. | 20 minutes ago Description :The WPML Multilingual CMS plugin for WordPress is vulnerable to Authentication Bypass via Race Condition in versions up to, and including, 4.9.7. This is due to the `process_iframe_request` function's language-per-domain SSO handler generating the cross-domain sign-in token via `wp_create_nonce('wpml_sso')` on the logout landing page, where the browser has already discarded its authentication cookies -- so `wp_get_session_token()` returns an empty string and the token collapses to the shared anonymous nonce for the current 12-hour tick rather than a user-bound secret -- and then storing it in the `wpml_sso_user__` transient mapped to the victim's `user_id` with no binding to the specific sign-out action or requesting client. Because an unauthenticated attacker can independently derive the identical token by triggering the logout confirmation flow on `wp-login.php?action=logout`, and because the `is_iframe_request()` gate conditions (the per-domain SSO `started` transient and domain-hash derived from the public constant `SSO_NONCE`) are fully computable within the 60-second `SSO_TIMEOUT` window, an unauthenticated attacker can submit the forged `wpml_sso_token_domain` parameter with a `wpml_user_signed_in` status to a secondary language-domain endpoint before the legitimate `wpml_user_signed_out` iframe fires, causing WordPress authentication cookies to be issued for the victim. This makes it possible for unauthenticated attackers to gain access to accounts of users -- including administrators -- who are actively in the process of logging out during the race window. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Connect Claude to PagerDuty Instantly with Claude Auto-Connect by Antonella Hidalgo Moreno

DevFeed: [Connect Claude to PagerDuty Instantly with Claude Auto-Connect by Antonella Hidalgo Moreno](<https://devfeed.tech/articles/connect-claude-to-pagerduty-instantly-with-claude-auto-connect-by-antonella-hidalgo-moreno-125681.md>)

Original publisher: [Read original article](<https://www.pagerduty.com/blog/announcements/claude-auto-connect/>)

Author: Antonella Hidalgo Moreno

Published: 2026-11-09T17:29:55Z

Content type: release

Language: en

Sources: [PagerDuty](<https://devfeed.tech/sources/pagerduty.md>)

Topics: [Claude](<https://devfeed.tech/topics/claude.md>), [AI connector platforms](<https://devfeed.tech/topics/ai-connector-platforms.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [actions](<https://devfeed.tech/tags/actions.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [benefit](<https://devfeed.tech/tags/benefit.md>), [claude](<https://devfeed.tech/tags/claude.md>), [incident-management-response](<https://devfeed.tech/tags/incident-management-response.md>), [operations](<https://devfeed.tech/tags/operations.md>), [pagerduty](<https://devfeed.tech/tags/pagerduty.md>)

### AI overview

PagerDuty's Claude auto-connect lets an administrator enable the MCP connector once for an organization, so members with matching PagerDuty accounts see it connected without individual sign-in or consent flows. Access ends automatically when a member leaves the Claude organization, at the next token renewal. The post says each PagerDuty action retains the employee's identity and existing permissions for audit accountability, while administrators set the allowed scopes. It is presented as avoiding the need for an identity-provider integration and reducing setup effort. The feature is in Early Access and is not currently part of PagerDuty's FedRAMP in-scope services.

### Source excerpt

This blog post is part of PagerDuty's ongoing series on how we're helping customers navigate their journey towards autonomous operations. Read on to learn about... The post Connect Claude to PagerDuty Instantly with Claude Auto-Connect appeared first on PagerDuty.

## Who is actually using your Snowflake MCP server?

DevFeed: [Who is actually using your Snowflake MCP server?](<https://devfeed.tech/articles/who-is-actually-using-your-snowflake-mcp-server-124191.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/who-is-actually-using-your-snowflake-mcp-server-683a6cb543d7?source=rss----34b6daafc07---4>)

Author: Ondřej Blaha

Published: 2026-11-09T15:01:04Z

Content type: article

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [JOIN](<https://devfeed.tech/topics/join.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [integration](<https://devfeed.tech/tags/integration.md>), [join](<https://devfeed.tech/tags/join.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [snowflake-cortex](<https://devfeed.tech/tags/snowflake-cortex.md>)

### AI overview

Snowflake does not record the MCP server name in query history, but it records the OAuth security integration used at login. Assigning a separate integration to each MCP server and joining QUERY_HISTORY.AUTHN_EVENT_ID to LOGIN_HISTORY.EVENT_ID lets teams attribute queries by integration, user, role, and time; a shared integration only identifies a group. The article explains how to configure OAuth integrations and build usage reports, while noting that login rows are not calls and that query counts can include procedure or dbt work and require filtering out Snowflake's automatic skills-list queries. PAT and key-pair sign-ins lack an integration name, so attribution is weaker. Cortex Analyst leaves tagged validation queries but does not execute returned SQL; Cortex Search activity generally cannot be tied to a user or channel in account usage. Query and login history are delayed, and some queries may be missing or sampled. The reported method is a workaround based on the author's internal October 2026 testing.

### Source excerpt

How to see who sends queries through MCP, how many and how often, using one join in account usageSnowflake has no column that tells you which MCP server a query came through. It does store the name of the OAuth security integration that every MCP client signs in with. Give each MCP server its own integration, join one column from query history to login history, and you have usage per server, user and day. This article shows how, and where the approach stops working. Setting up a Snowflake-managed MCP server takes a few minutes. A few weeks later, the same client usually comes back with a different question: is anyone using it? Which users, how often, and is it worth it? I get this question from clients regularly. The last one put it as a requirement: a model that contains only queries run by their reporting team through one specific MCP server, without the same people's Snowsight work, and with user, role, timestamp and volume. Two identical rows in query history My first thought was that a filter on query history would do it. It won't, because query history has no column that says "this came from MCP server X", and I did not find one anywhere else in account usage either. That client's reporting team works in Snowsight every day and has recently started asking Claude as well. When an analyst writes select region, sum(revenue) from sales in a worksheet and later asks Claude the same question, Claude sends the same SQL through the MCP server. QUERY_HISTORY then holds two rows with the same text, the same user, the same role and, if the warehouse is shared, the same warehouse.The two queries differ only in how the analyst signed in.The sign-in tells them apart An MCP client such as Claude Desktop, Claude Code or Cursor signs in through an OAuth security integration, while Snowsight uses SSO or a password. Snowflake stores the name of the integration with every login, and every query points to the login that opened its session, so all it takes is one join: select q.que

## How to add authentication to a Rust axum app with WorkOS AuthKit

DevFeed: [How to add authentication to a Rust axum app with WorkOS AuthKit](<https://devfeed.tech/articles/how-to-add-authentication-to-a-rust-axum-app-with-workos-authkit-123473.md>)

Original publisher: [Read original article](<https://workos.com/blog/rust-axum-authentication-authkit>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Rust](<https://devfeed.tech/topics/rust.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [client library](<https://devfeed.tech/topics/client-library.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [request](<https://devfeed.tech/tags/request.md>), [rust](<https://devfeed.tech/tags/rust.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [service](<https://devfeed.tech/tags/service.md>), [webhook](<https://devfeed.tech/tags/webhook.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

The WorkOS Rust SDK lets an axum service authenticate with AuthKit using sealed session cookies and locally verified access tokens. The source outlines the flow: build and share a client, create a PKCE authorization URL while storing the verifier and state in a short-lived sealed cookie, exchange the callback code, then authenticate the session on each request. Cookie passwords must be 64-character hex strings; the Rust cookie format is not compatible with other WorkOS SDKs. Local verification fetches and caches signing keys, but cannot detect session revocation until the access token expires, so the source recommends webhook handling and rechecks before destructive operations when revocation matters. For webhooks, verify the signature against the timestamp and exact raw body before parsing; deliveries may repeat or arrive out of order, so record processed event IDs and return 200 promptly. SDK retries cover 429s, 5xxs and retryable transport errors, but unsafe HTTP methods retry only when given an idempotency key--and only if the endpoint deduplicates it.

### Source excerpt

Use the WorkOS Rust SDK to sign users in with AuthKit, verify their session on every request, and check webhook signatures in an axum service.

## SSO is broken? The answer is already in your session log

DevFeed: [SSO is broken? The answer is already in your session log](<https://devfeed.tech/articles/sso-is-broken-the-answer-is-already-in-your-session-log-124330.md>)

Original publisher: [Read original article](<https://workos.com/blog/sso-broken-session-log>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [log management](<https://devfeed.tech/topics/log-management.md>)

Tags: [configuration](<https://devfeed.tech/tags/configuration.md>), [customer](<https://devfeed.tech/tags/customer.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [events](<https://devfeed.tech/tags/events.md>), [failed](<https://devfeed.tech/tags/failed.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [it](<https://devfeed.tech/tags/it.md>), [sso](<https://devfeed.tech/tags/sso.md>), [status](<https://devfeed.tech/tags/status.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS session logs can pinpoint where an SSO failure occurs and who can fix it. In the dashboard, filter a connection's Sessions tab by email, status, origin or time, then inspect the IdP request, response and any error. Success shifts investigation to app handling or authorization; failed sessions may point to the IdP or to your attribute mapping. Required attributes that are missing can fail sign-in, while unmapped optional attributes return null and may leave a successful session with empty fields. Origin helps distinguish app-started, IdP-started and Admin Portal test flows; OIDC is SP-initiated only. For patterns, use SSO events with connection IDs and error details: stream them to Datadog or count failures by connection through the cursor-paginated Events API. When the IdP is responsible, share the session ID, timestamp, status and response with its administrator.

### Source excerpt

Every WorkOS SSO attempt records its status, origin and the IdP's response. Read it in five minutes and know whether the fix is yours or the customer's.

[Next page](<https://devfeed.tech/topics/sso.md?cursor=WyIyMDI2LTExLTA5VDAwOjAwOjAwKzAwOjAwIiwgImJhNTc4YWY2LWNlNTMtNGI0ZS1hOGVlLWVkYTc4NTU5YzdlNSJd>)