# Why Rely on a Social Auth Library?

The use of a reusable social-auth layer to standardize OAuth2 provider integration and abstract provider-specific authentication details.

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

## 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.

## Announcing six new OAuth2 login providers in Appwrite Auth

DevFeed: [Announcing six new OAuth2 login providers in Appwrite Auth](<https://devfeed.tech/articles/announcing-six-new-oauth2-login-providers-in-appwrite-auth-91187.md>)

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

Author: Aditya Oberai

Published: 2026-10-19T00: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>), [Server-side vs Client-side OAuth2 Flows](<https://devfeed.tech/topics/server-side-vs-client-side-oauth2-flows.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [hugging face](<https://devfeed.tech/topics/hugging-face.md>), [webflow](<https://devfeed.tech/topics/webflow.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account](<https://devfeed.tech/tags/account.md>), [added](<https://devfeed.tech/tags/added.md>), [admin](<https://devfeed.tech/tags/admin.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-developers](<https://devfeed.tech/tags/ai-developers.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [app](<https://devfeed.tech/tags/app.md>), [auth](<https://devfeed.tech/tags/auth.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [hugging-face](<https://devfeed.tech/tags/hugging-face.md>), [login](<https://devfeed.tech/tags/login.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [providers](<https://devfeed.tech/tags/providers.md>), [server](<https://devfeed.tech/tags/server.md>), [tiktok](<https://devfeed.tech/tags/tiktok.md>), [webflow](<https://devfeed.tech/tags/webflow.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Appwrite Auth adds six OAuth2 providers--Hugging Face, Resend, Cloudflare, TikTok, Kakao, and Webflow--using the existing login APIs. Enable each provider in the Console with its client credentials; server apps can use createOAuth2Token and createSession, while browser apps use createOAuth2Session. Appwrite handles PKCE for Resend and Cloudflare, and provider access tokens are available for supported API access. Provider data differs: TikTok and Resend provide no email; Cloudflare and Webflow emails are unverified; Hugging Face and Kakao emails are marked verified only when the provider confirms them. Unverified email matches do not automatically sign into existing accounts; users can link identities after signing in. Resend requires an explicit scope, and Kakao scopes must be enabled as consent items or authorization can fail with KOE205. All six are on Appwrite Cloud; self-hosted availability spans versions 2.0 through 2.4.

### Source excerpt

Appwrite Auth now supports OAuth2 login with Hugging Face, Resend, Cloudflare, TikTok, Kakao, and Webflow. See what each returns and how to add it to a server-side app.

## auth.md -- agent registration instructions

DevFeed: [auth.md -- agent registration instructions](<https://devfeed.tech/articles/auth-md-agent-registration-instructions-89076.md>)

Original publisher: [Read original article](<https://specification.website/spec/agent-readiness/auth-md/>)

Author: Joost de Valk

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

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Why Rely on a Social Auth Library?](<https://devfeed.tech/topics/why-rely-on-a-social-auth-library.md>)

Tags: [agent-readiness](<https://devfeed.tech/tags/agent-readiness.md>), [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [optional](<https://devfeed.tech/tags/optional.md>), [permissions](<https://devfeed.tech/tags/permissions.md>)

### AI overview

The article explains auth.md, an emerging convention for documenting how agents register with a service and obtain scoped API access. It describes the OAuth metadata and implementation workflow, clarifies that the convention is not an IETF standard, and emphasizes that services must enforce permissions and security checks server-side.

### Source excerpt

An auth.md file tells agents how to register with a service and obtain scoped API access. An emerging convention for services that support agent registration, backed by OAuth metadata and server-enforced permissions.

## Using on-behalf-of flow for Entra-based MCP servers

DevFeed: [Using on-behalf-of flow for Entra-based MCP servers](<https://devfeed.tech/articles/using-on-behalf-of-flow-for-entra-based-mcp-servers-21745.md>)

Original publisher: [Read original article](<http://blog.pamelafox.org/2026/01/using-on-behalf-of-flow-for-entra-based.html>)

Author: Pamela Fox (noreply@blogger.com)

Published: 2026-01-16T20:34:00Z

Content type: tutorial

Language: en

Sources: [Pamela Fox](<https://devfeed.tech/sources/pamela-fox.md>)

Topics: [Entra ID](<https://devfeed.tech/topics/entra-id.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Why Rely on a Social Auth Library?](<https://devfeed.tech/topics/why-rely-on-a-social-auth-library.md>)

Tags: [delegation](<https://devfeed.tech/tags/delegation.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [mcp-servers](<https://devfeed.tech/tags/mcp-servers.md>), [microsoft-entra](<https://devfeed.tech/tags/microsoft-entra.md>), [microsoft-graph](<https://devfeed.tech/tags/microsoft-graph.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [onedrive](<https://devfeed.tech/tags/onedrive.md>), [pattern](<https://devfeed.tech/tags/pattern.md>), [python](<https://devfeed.tech/tags/python.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

### AI overview

For a Python FastMCP MCP server that needs to call another API as the signed-in user, the excerpt identifies OAuth on-behalf-of (OBO), or delegation, as the mechanism--for example, to query Microsoft Graph. It explains that Microsoft Entra provides authorization server metadata but supports neither Dynamic Client Registration (DCR) nor Client ID Metadata Documents (CIMD). That is sufficient when the server is limited to pre-authorized clients; arbitrary MCP clients require DCR or CIMD. FastMCP addresses the DCR gap with an OAuth proxy that acts as the authorization server, forwards requests to Entra when needed, and stores client information in a designated database. The excerpt cuts off during its database example, so it does not establish implementation details beyond that.

### Source excerpt

In December, we presented a series about MCP, culminating in a session about adding authentication to MCP servers. I demoed a Python MCP server that uses Microsoft Entra for authentication, requiring users to first login to the Microsoft tenant before they could use a tool. Many developers asked how they could take the Entra integration further, like to check the user's group membership or query their OneDrive. That requires using an "on-behalf-of" flow, also known as "delegation" in OAuth, where the MCP server uses the user's identity to call another API, like the Microsoft Graph API. In this blog post, I will explain how to use Entra with OBO flow in a Python FastMCP server. How MCP servers can use Entra authentication The MCP authorization specification is based on OAuth2, but with some additional features tacked on top. Every MCP client is actually an OAuth2 client, and each MCP server is an OAuth2 resource server. MCP auth adds these features to help clients determine how to authorize a server: Protected resource metadata (PRM): Implemented on the MCP server, provides details about the authorization server and method Authorization server metadata: Implemented on the authorization server, gives URLs for OAuth2 endpoints Additionally, to allow MCP servers to work with arbitrary MCP clients, MCP auth supports either of these client registration methods: Dynamic Client Registration (DCR): Implemented on the authorization server, it can register new MCP clients as OAuth2 clients, even if it hasn't seen them before. Client ID Metadata Documents (CIMD): An alternative to DCR, this requires both the MCP client to make a CIMD document available on a server, and requires the authorization server to fetch the CIMD document for details about the client. Microsoft Entra does support authorization server metadata, but it does not support either DCR or CIMD. That's actually fine if you are building an MCP server that's only going to be used with pre-authorized clients, like i

## Authentication Best Practices: Convex, Clerk and Next.js

DevFeed: [Authentication Best Practices: Convex, Clerk and Next.js](<https://devfeed.tech/articles/authentication-best-practices-convex-clerk-and-next-js-81278.md>)

Original publisher: [Read original article](<https://stack.convex.dev/authentication-best-practices-convex-clerk-and-nextjs>)

Author: Stack

Published: 2025-03-06T18:45:35Z

Content type: tutorial

Language: en

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

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Security](<https://devfeed.tech/topics/security.md>), [Why Rely on a Social Auth Library?](<https://devfeed.tech/topics/why-rely-on-a-social-auth-library.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [convex](<https://devfeed.tech/tags/convex.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [security](<https://devfeed.tech/tags/security.md>), [walkthroughs](<https://devfeed.tech/tags/walkthroughs.md>)

### AI overview

The article explains how authentication timing can create race conditions and security risks in Convex applications using Clerk and Next.js. It recommends validating authentication on the server, client, and Convex backend, and demonstrates middleware, skipped queries, backend checks, and reusable hooks.

### Source excerpt

Authentication issues in real-time applications can cause security risks, especially when client-side queries run before validation. Ensuring authentication at the server (Next.js middleware), client (useConvexAuth()), and database (Convex functions) helps prevent unauthorized access. Using middleware, enforcing authentication in Convex functions, and leveraging custom hooks improves security and performance.

## Convex with Auth.js (NextAuth)

DevFeed: [Convex with Auth.js (NextAuth)](<https://devfeed.tech/articles/convex-with-auth-js-nextauth-81412.md>)

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

Author: Stack

Published: 2024-05-07T14:03:00Z

Content type: tutorial

Language: en

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

Topics: [Why Rely on a Social Auth Library?](<https://devfeed.tech/topics/why-rely-on-a-social-auth-library.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [account](<https://devfeed.tech/topics/account.md>)

Tags: [async](<https://devfeed.tech/tags/async.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [await](<https://devfeed.tech/tags/await.md>), [backend](<https://devfeed.tech/tags/backend.md>), [convex](<https://devfeed.tech/tags/convex.md>), [database](<https://devfeed.tech/tags/database.md>), [integration](<https://devfeed.tech/tags/integration.md>), [next](<https://devfeed.tech/tags/next.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [walkthroughs](<https://devfeed.tech/tags/walkthroughs.md>)

### AI overview

A tutorial on integrating Auth.js (formerly NextAuth) with a Next.js app and Convex backend. It covers OAuth and email magic-link providers, configuring Convex as the Auth.js database adapter, authenticating Convex functions, and handling sign-in, sign-out, redirects, and session IDs. The article cautions that developers are responsible for verifying the security of their implementation.

### Source excerpt

Learn how to use Auth.js with your Next.js server and Convex backend to build a full-featured authentication system.

## Convex Adapter for Auth.js (NextAuth) Setup Guide

DevFeed: [Convex Adapter for Auth.js (NextAuth) Setup Guide](<https://devfeed.tech/articles/convex-adapter-for-auth-js-nextauth-setup-guide-81413.md>)

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

Author: Stack

Published: 2024-05-07T11:47:00Z

Content type: tutorial

Language: en

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

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

Tags: [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [guide](<https://devfeed.tech/tags/guide.md>), [integration](<https://devfeed.tech/tags/integration.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [setup](<https://devfeed.tech/tags/setup.md>)

### AI overview

A setup guide explains how to install and configure a Convex adapter for Auth.js in a Next.js application. It covers database schemas and adapter endpoints, shared-secret protection, and JWT-based authentication that connects Auth.js sessions to Convex.

### Source excerpt

Learn how to install and configure the Convex adapter for Auth.js as part of getting set up with Convex and Next.js.

## Devise for Ruby on Rails: Setup, Modules & Rails 8 Auth

DevFeed: [Devise for Ruby on Rails: Setup, Modules & Rails 8 Auth](<https://devfeed.tech/articles/devise-for-ruby-on-rails-setup-modules-rails-8-auth-61670.md>)

Original publisher: [Read original article](<https://blog.appsignal.com/2023/07/12/an-introduction-to-devise-for-ruby-on-rails.html>)

Author: Aestimo Kirina

Published: 2023-07-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [AppSignal](<https://devfeed.tech/sources/appsignal.md>)

Topics: [Ruby on Rails](<https://devfeed.tech/topics/ruby-on-rails.md>), [Why Rely on a Social Auth Library?](<https://devfeed.tech/topics/why-rely-on-a-social-auth-library.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [database](<https://devfeed.tech/tags/database.md>), [devise](<https://devfeed.tech/tags/devise.md>), [locking](<https://devfeed.tech/tags/locking.md>), [rails](<https://devfeed.tech/tags/rails.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [ruby](<https://devfeed.tech/tags/ruby.md>)

### AI overview

This tutorial introduces Devise, a modular authentication gem for Ruby on Rails, and explains its setup, modules, helpers, and production considerations. It compares Devise with Rails 8's built-in authentication generator and outlines when each option may fit.

### Source excerpt

Devise is a full-featured Rails authentication gem built on Warden. Install it, use its 10 modules, and see when to pick it over Rails 8's built-in auth.

## Plans to Re-enable the GitHub Integration

DevFeed: [Plans to Re-enable the GitHub Integration](<https://devfeed.tech/articles/plans-to-re-enable-the-github-integration-26407.md>)

Original publisher: [Read original article](<https://www.heroku.com/blog/github-integration-update/>)

Author: Shyam Subramanyan

Published: 2022-05-19T17:58:00Z

Content type: news

Language: en

Sources: [Heroku](<https://devfeed.tech/sources/heroku.md>)

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Why Rely on a Social Auth Library?](<https://devfeed.tech/topics/why-rely-on-a-social-auth-library.md>), [GitHub API](<https://devfeed.tech/topics/github-api.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [apis](<https://devfeed.tech/tags/apis.md>), [commit](<https://devfeed.tech/tags/commit.md>), [commits](<https://devfeed.tech/tags/commits.md>), [connect](<https://devfeed.tech/tags/connect.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [github](<https://devfeed.tech/tags/github.md>), [github-apps](<https://devfeed.tech/tags/github-apps.md>), [github-integration](<https://devfeed.tech/tags/github-integration.md>), [heroku](<https://devfeed.tech/tags/heroku.md>), [integration](<https://devfeed.tech/tags/integration.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [need](<https://devfeed.tech/tags/need.md>), [news](<https://devfeed.tech/tags/news.md>), [notify](<https://devfeed.tech/tags/notify.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [repo](<https://devfeed.tech/tags/repo.md>), [review](<https://devfeed.tech/tags/review.md>), [scope](<https://devfeed.tech/tags/scope.md>), [security](<https://devfeed.tech/tags/security.md>), [security-incidents](<https://devfeed.tech/tags/security-incidents.md>)

### AI overview

Heroku's security review cleared its GitHub integration for re-enablement, while identifying that its OAuth `repo` scope grants broader access than the integration needs. That scope supports pipeline connections, monitoring commits and pull requests, and writing commit and deploy statuses. Heroku said it was exploring GitHub Apps for more granular permissions and RFC8705 to better protect OAuth tokens, but those changes required work by both companies. The May 25, 2022 update says the integration is re-enabled: users can reconnect with newly generated tokens or wait for the enhanced integration. Heroku recommended `git push heroku` to keep services running until reconnecting.

### Source excerpt

[Update: May 25, 2022 - GitHub integration is now re-enabled. You can connect to GitHub immediately or wait for the enhanced integration as described below. To re-establish your GitHub connection now, please follow these instructions.] We know you are waiting for us to re-enable our integration with GitHub, and we've committed to you that we [...] The post Plans to Re-enable the GitHub Integration appeared first on Heroku.