Bug Report: MuleSoft Anypoint Code Builder extension OAuth authentication fails
Environment
-
macOS (Apple Silicon)
-
MuleSoft extensions:
-
salesforce.mule-dx-vscode 5.4.3
-
salesforce.mule-dx-api-component 4.8.2
-
salesforce.mule-dx-mule-dev-component 3.16.0
Description
The MuleSoft Anypoint Code Builder extension initiates OAuth authentication correctly, but fails to complete the authentication flow. The extension redirects to a cursor:// protocol URL, which is received by macOS (security prompt appears), but Cursor doesn’t properly process the callback. After exactly 5 minutes, authentication times out with “Sign in failed: Sign in Anypoint timed out!”.
Steps to Reproduce
-
Install MuleSoft Anypoint Code Builder extension in Cursor
-
Attempt to authenticate with Anypoint Platform through the extension
-
When prompted, approve the system dialog for the cursor:// protocol
-
Complete authentication on the Anypoint Platform website
-
Observe that the authentication never completes in Cursor
Expected vs Actual Behavior
-
Expected: Authentication completes successfully, allowing access to MuleSoft features
-
Actual: After authentication on Anypoint Platform, the callback to Cursor via cursor:// protocol fails to complete the OAuth flow, timing out after 5 minutes
Technical Details
Log entries show:
text
Apply to cursor-redir…
“About to redirect user using callback: cursor://salesforce.mule-dx-vscode/oauth/anypoint/callback?windowId=2”
…
“Sign in failed: Sign in Anypoint timed out!” (5 minutes later)
Manually triggering the callback URL via a script doesn’t update the extension logs at all, indicating Cursor isn’t properly routing the protocol URL to the extension.
This is a blocking issue for MuleSoft development in Cursor. The same extension works correctly in VS Code, suggesting Cursor’s protocol URL handler implementation differs from VS Code’s in a way that breaks the extension’s OAuth flow.