Fix Slack OAuth authorize URL path

[galvana]

Description Of Changes

Fix the Slack OAuth authorize URL in the admin UI. The frontend was navigating to /api/v1/plus/chat/authorize but the backend route is mounted at /api/v1/plus/chat/slack/authorize, resulting in a 404 when users clicked "Authorize" to initiate the Slack OAuth flow.

Code Changes

• clients/admin-ui/src/features/chat-provider/forms/SlackChatForm.tsx - Fix authorize URL from /chat/authorize to /chat/slack/authorize (with and without config_id)
• clients/admin-ui/src/features/chat-provider/ChatConfigurations.tsx - Fix authorize URL in the configurations table "Authorize" button

Steps to Confirm

1. Navigate to the Chat Provider settings page in the admin UI
2. Configure a Slack chat provider with client ID and secret
3. Click "Authorize" — should redirect to Slack's OAuth page instead of returning a 404

Pre-Merge Checklist

• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• UX feedback:
  • No UX review needed
• Followup issues:
  • No followup issues
• Database migrations:
  • No migrations
• Documentation:
  • No documentation updates required

Made with Cursor

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	Feb 24, 2026 0:31am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		Feb 24, 2026 0:31am

[greptile-apps]

Greptile Summary

Fixed the Slack OAuth authorize URL path from /api/v1/plus/chat/authorize to /api/v1/plus/chat/slack/authorize to match the backend route, resolving 404 errors when users clicked "Authorize" to initiate the Slack OAuth flow.

• Updated authorize URL in ChatConfigurations.tsx Authorize button (line 224)
• Updated authorize URL in SlackChatForm.tsx handleAuthorize function for both paths with and without config_id parameter (lines 148-149)
• Added changelog entry documenting the fix

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are straightforward URL path corrections that fix a bug. The fix is applied consistently across both locations where the authorize URL is used, and the pattern follows the existing OAuth authorize URL pattern seen elsewhere in the codebase (e.g., /api/v1/plus/openid-provider/{identifier}/authorize). The changes are minimal, well-scoped, and fix a functional bug without introducing new logic or complexity.
• No files require special attention

Important Files Changed

Filename	Overview
changelog/7466-fix-slack-authorize-url.yaml	Added changelog entry documenting the Slack OAuth URL fix
clients/admin-ui/src/features/chat-provider/ChatConfigurations.tsx	Fixed authorize URL in the Authorize button from /chat/authorize to /chat/slack/authorize
clients/admin-ui/src/features/chat-provider/forms/SlackChatForm.tsx	Fixed authorize URL in handleAuthorize function from /chat/authorize to /chat/slack/authorize

_{Last reviewed commit: 21bdd7c}

[greptile-apps]

_{3 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[thabofletcher]

Thanks for the quick fix @galvana!