Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Jan 5, 2026

Summary

Adds a changelog entry for January 6, 2026 announcing the upcoming mandatory Link auth flow for Composio-managed OAuth connections, with a phased rollout timeline.

Changes

  • Added new changelog file fern/pages/src/changelog/01-06-26.md
  • Documents the phased rollout timeline:
    • January 06, 2026 - Option to enable Link auth flow available in Project Config
    • February 21, 2026 - Enabled by default for new organizations
    • April 06, 2026 - Enabled for all organizations
  • Explains the security benefits and how users can opt-in early via Project Config
  • Uses "custom auth" terminology for users with their own OAuth credentials
  • Added callout note clarifying this is not a backward breaking change (OAuth flow UX will change for end users)
  • Added screenshot showing the Project Config toggle

Type of change

  • Documentation

How Has This Been Tested?

Documentation-only change. Verified the file follows the existing changelog format and naming convention.

Test Plan:

  • Verified the changelog file follows the existing naming convention (MM-DD-YY.md)
  • Confirmed content structure matches other changelog entries in the directory

Screenshots

Enable Link Flow for Managed Auth

Checklist

  • I have read the Code of Conduct and this PR adheres to it
  • I ran linters/tests locally and they passed
  • I updated documentation as needed
  • I added tests or explain why not applicable - N/A, documentation only
  • I added a changeset if this change affects published packages - N/A, documentation only

Human Review Checklist

  • Verify the rollout dates are correct (Jan 06, Feb 21, Apr 06 2026)
  • Confirm the flag name enableLinkFlowForManagedAuth matches the UI implementation
  • Verify "custom auth" is the correct terminology for users with their own OAuth credentials
  • Review the callout wording about non-breaking change is accurate
  • Verify the screenshot displays correctly and matches current UI

Additional context

Link to Devin run: https://app.devin.ai/sessions/bf3331cf4b9b494abbda4c1007fa600b
Requested by: [email protected] ([email protected])

@devin-ai-integration
Copy link
Contributor Author

Original prompt from [email protected]
Add changelog  for Jan6 in changelog and in frontend add option in project config to enable is_composio_link_enabled_for_managed_auth

## 🔐 Mandatory Link Auth for Composio-Managed OAuth

### What’s Changing

Starting **February 15, 2026**, all OAuth connections that use **Composio-managed credentials** will automatically use the **Link Auth** flow.

- ✅ **No action required** on your side  
- ✨ A small **UX change** during OAuth to improve platform security  

👉 **No changes** if you use your own `client_id` and `client_secret`.

---

### Why This Change

To align with modern OAuth security best practices, we’re standardizing on Link Auth for all Composio-managed OAuth connections.

Link Auth ensures:

- 🔒 **Secure, token-bound OAuth initiation**
- 🛡️ **Full protection against OAuth account takeover** : This guarantees OAuth connections are created only by the intended user, for the intended project, and within the correct security context.

---

### Enable & Test Early (Optional)

You can opt in before **February 15, 2026** to preview and test the new behavior.

**How to enable:**
1. Go to your **Project Config** page
2. Enable the flag:  
   `enableLinkFlowForManagedAuth`

Once enabled, all new OAuth connections using Composio-managed credentials will follow the Link Auth flow.

@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@vercel
Copy link

vercel bot commented Jan 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
fumadocs Error Error Jan 6, 2026 7:01am

@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026


- No action required on your side
- A small UX change during OAuth to improve platform security
- No changes if you use your own `client_id` and `client_secret`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

custom auth

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to use "Link auth flow" and "custom auth" terminology as requested.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

@github-actions
Copy link
Contributor

github-actions bot commented Jan 5, 2026

@himanshu-dixit
Copy link
Member

Devin add this screenshot Screenshot 2026-01-06 at 12 28 06 PM

@himanshu-dixit
Copy link
Member

Add callout that this is not backward breaking change but flow is going to change for end users.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2026

@devin-ai-integration
Copy link
Contributor Author

Added the screenshot and a callout note clarifying this is not a backward breaking change but the OAuth flow will change for end users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants