Skip to content

fix: allow custom URI schemes in OAuth Dynamic Client Registration - #2286

Closed
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom
ItsYash1421:fix/oauth-custom-uri-schemes
Closed

fix: allow custom URI schemes in OAuth Dynamic Client Registration#2286
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom
ItsYash1421:fix/oauth-custom-uri-schemes

Conversation

@ItsYash1421

@ItsYash1421ItsYash1421 commented Dec 9, 2025

Copy link
Copy Markdown

What kind of change does this PR introduce?

Bug fix - Fixes OAuth Dynamic Client Registration to support custom URI schemes

What is the current behavior?

Issue:#2285

The OAuth 2.0 Dynamic Client Registration endpoint (POST /oauth/clients/register) rejects custom URI schemes (e.g., cursor://, exp://, myapp://) even when they are explicitly whitelisted in the additional_redirect_urls configuration or GOTRUE_URI_ALLOW_LIST environment variable.

Current Error

{
"code": 400,
"error_code": "validation_failed",
"msg": "400: invalid redirect_uri 'cursor://anysphere.cursor-mcp/callback': scheme must be HTTPS or HTTP (localhost only)"
}

Root Cause

The OAuth server's client registration logic uses strict validation that only allows http and https schemes, which is inconsistent with PR #711 that relaxed this validation for general auth flows to support native applications.

What is the new behavior?

The OAuth server now uses the same allow-list-based validation as the rest of the auth system (introduced in PR #711). Custom URI schemes work when explicitly configured in the allow list.

Test Results

All validation tests pass successfully:

![Test Results]
Screenshot 2025-12-09 at 12 06 06 PM
Screenshot 2025-12-09 at 12 06 27 PM
Screenshot 2025-12-09 at 12 06 45 PM

PASS: TestValidateRequestOrigin (9 test cases)
PASS: TestValidateRequestOriginEdgeCases (5 test cases)
PASS: TestInferClientTypeFromAuthMethod (5 test cases)
PASS: TestGetValidAuthMethodsForClientType (4 test cases)
PASS: TestValidateClientTypeConsistency (8 test cases)
PASS: TestDetermineClientType (7 test cases)
PASS: TestIsValidAuthMethodForClientType (7 test cases)
PASS: TestValidateClientAuthentication (5 test cases)
PASS: TestGetAllValidAuthMethods
Total: 8 test suites, 40+ test cases - ALL PASS

Additional context

Changes Made

Files Modified:

  1. internal/api/oauthserver/service.go (~40 lines)

    • Changed validateRedirectURI() to use utilities.IsRedirectURLValid()
    • Updated validation methods to be Server methods for config access
    • Modified validate() methods to accept *Server parameter

  2. internal/api/oauthserver/service_test.go (~80 lines)

    • Updated TestRedirectURIValidation() to use new method signature
    • Added comprehensive TestCustomURISchemes() test
    • Updated SetupTest() to configure test URIs

References

@ItsYash1421
ItsYash1421 requested a review from a team as a code ownerDecember 9, 2025 06:59
depthfirst-app[bot]
depthfirst-appBot reviewed Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go Outdated
depthfirst-app[bot]
depthfirst-appBot reviewed Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go Outdated
@cemalkilic

cemalkilic commented Dec 16, 2025

Copy link
Copy Markdown
Contributor

Hi @ItsYash1421, thank you for opening this PR! 🙏

There seems to be a bit of confusion here. There are two different redirect URL systems:

  1. Supabase Auth Login Redirects - Where to send YOUR users after they log into your app using Supabase Auth, allowed list is config.URIAllowListMap

  2. OAuth Client Redirect URIs - Where to send users when a THIRD-PARTY app uses Supabase Auth as their OAuth provider. This is what issue OAuth Dynamic Client Registration rejects custom URI schemes (inconsistency with PR #711) #2285 is about and it shouldn't be related to config.URIAllowListMap at all.

Closing this PR in favor of #2298, but really appreciate you taking the time to help!

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

Reviewers

@depthfirst-appdepthfirst-app[bot]depthfirst-app[bot] left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@ItsYash1421@cemalkilic@YashKumarMeena001
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
fix: allow custom URI schemes in OAuth Dynamic Client Registration by ItsYash1421 · Pull Request #2286 · supabase/auth · GitHub
Skip to content
fix: allow custom URI schemes in OAuth Dynamic Client Registration - #2286
Closed
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Closed
fix: allow custom URI schemes in OAuth Dynamic Client Registration#2286
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Conversation
@ItsYash1421
@ItsYash1421ItsYash1421
commented
Dec 9, 2025

Copy link


Copy Markdown

What kind of change does this PR introduce?
Bug fix - Fixes OAuth Dynamic Client Registration to support custom URI schemes
What is the current behavior?
Issue:#2285
The OAuth 2.0 Dynamic Client Registration endpoint (POST /oauth/clients/register) rejects custom URI schemes (e.g., cursor://, exp://, myapp://) even when they are explicitly whitelisted in the additional_redirect_urls configuration or GOTRUE_URI_ALLOW_LIST environment variable.
Current Error
{
"code": 400,
"error_code": "validation_failed",
"msg": "400: invalid redirect_uri 'cursor://anysphere.cursor-mcp/callback': scheme must be HTTPS or HTTP (localhost only)"
}
Root Cause
The OAuth server's client registration logic uses strict validation that only allows http and https schemes, which is inconsistent with PR #711 that relaxed this validation for general auth flows to support native applications.
What is the new behavior?
The OAuth server now uses the same allow-list-based validation as the rest of the auth system (introduced in PR #711). Custom URI schemes work when explicitly configured in the allow list.
Test Results
All validation tests pass successfully:
![Test Results]
Screenshot 2025-12-09 at 12 06 06 PM
Screenshot 2025-12-09 at 12 06 27 PM
Screenshot 2025-12-09 at 12 06 45 PM
PASS: TestValidateRequestOrigin (9 test cases)
PASS: TestValidateRequestOriginEdgeCases (5 test cases)
PASS: TestInferClientTypeFromAuthMethod (5 test cases)
PASS: TestGetValidAuthMethodsForClientType (4 test cases)
PASS: TestValidateClientTypeConsistency (8 test cases)
PASS: TestDetermineClientType (7 test cases)
PASS: TestIsValidAuthMethodForClientType (7 test cases)
PASS: TestValidateClientAuthentication (5 test cases)
PASS: TestGetAllValidAuthMethods
Total: 8 test suites, 40+ test cases - ALL PASS 
Additional context
Changes Made
Files Modified:
  1. internal/api/oauthserver/service.go (~40 lines)
    • Changed validateRedirectURI() to use utilities.IsRedirectURLValid()
    • Updated validation methods to be Server methods for config access
    • Modified validate() methods to accept *Server parameter
  2. internal/api/oauthserver/service_test.go (~80 lines)
    • Updated TestRedirectURIValidation() to use new method signature
    • Added comprehensive TestCustomURISchemes() test
    • Updated SetupTest() to configure test URIs
References
@ItsYash1421
ItsYash1421
requested a review
from a team
as a code ownerDecember 9, 2025 06:59
depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

@cemalkilic
cemalkilic
commented
Dec 16, 2025

Copy link


Copy Markdown

Contributor
Hi @ItsYash1421, thank you for opening this PR! 🙏
There seems to be a bit of confusion here. There are two different redirect URL systems:
  1. Supabase Auth Login Redirects - Where to send YOUR users after they log into your app using Supabase Auth, allowed list is config.URIAllowListMap
  2. OAuth Client Redirect URIs - Where to send users when a THIRD-PARTY app uses Supabase Auth as their OAuth provider. This is what issue OAuth Dynamic Client Registration rejects custom URI schemes (inconsistency with PR #711) #2285 is about and it shouldn't be related to config.URIAllowListMap at all.
Closing this PR in favor of #2298, but really appreciate you taking the time to help!
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@depthfirst-appdepthfirst-app[bot]depthfirst-app[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@ItsYash1421@cemalkilic@YashKumarMeena001

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
fix: allow custom URI schemes in OAuth Dynamic Client Registration by ItsYash1421 · Pull Request #2286 · supabase/auth · GitHub
Skip to content
fix: allow custom URI schemes in OAuth Dynamic Client Registration - #2286
Closed
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Closed
fix: allow custom URI schemes in OAuth Dynamic Client Registration#2286
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Conversation
@ItsYash1421
@ItsYash1421ItsYash1421
commented
Dec 9, 2025

Copy link


Copy Markdown

What kind of change does this PR introduce?
Bug fix - Fixes OAuth Dynamic Client Registration to support custom URI schemes
What is the current behavior?
Issue:#2285
The OAuth 2.0 Dynamic Client Registration endpoint (POST /oauth/clients/register) rejects custom URI schemes (e.g., cursor://, exp://, myapp://) even when they are explicitly whitelisted in the additional_redirect_urls configuration or GOTRUE_URI_ALLOW_LIST environment variable.
Current Error
{
"code": 400,
"error_code": "validation_failed",
"msg": "400: invalid redirect_uri 'cursor://anysphere.cursor-mcp/callback': scheme must be HTTPS or HTTP (localhost only)"
}
Root Cause
The OAuth server's client registration logic uses strict validation that only allows http and https schemes, which is inconsistent with PR #711 that relaxed this validation for general auth flows to support native applications.
What is the new behavior?
The OAuth server now uses the same allow-list-based validation as the rest of the auth system (introduced in PR #711). Custom URI schemes work when explicitly configured in the allow list.
Test Results
All validation tests pass successfully:
![Test Results]
Screenshot 2025-12-09 at 12 06 06 PM
Screenshot 2025-12-09 at 12 06 27 PM
Screenshot 2025-12-09 at 12 06 45 PM
PASS: TestValidateRequestOrigin (9 test cases)
PASS: TestValidateRequestOriginEdgeCases (5 test cases)
PASS: TestInferClientTypeFromAuthMethod (5 test cases)
PASS: TestGetValidAuthMethodsForClientType (4 test cases)
PASS: TestValidateClientTypeConsistency (8 test cases)
PASS: TestDetermineClientType (7 test cases)
PASS: TestIsValidAuthMethodForClientType (7 test cases)
PASS: TestValidateClientAuthentication (5 test cases)
PASS: TestGetAllValidAuthMethods
Total: 8 test suites, 40+ test cases - ALL PASS 
Additional context
Changes Made
Files Modified:
  1. internal/api/oauthserver/service.go (~40 lines)
    • Changed validateRedirectURI() to use utilities.IsRedirectURLValid()
    • Updated validation methods to be Server methods for config access
    • Modified validate() methods to accept *Server parameter
  2. internal/api/oauthserver/service_test.go (~80 lines)
    • Updated TestRedirectURIValidation() to use new method signature
    • Added comprehensive TestCustomURISchemes() test
    • Updated SetupTest() to configure test URIs
References
@ItsYash1421
ItsYash1421
requested a review
from a team
as a code ownerDecember 9, 2025 06:59
depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

@cemalkilic
cemalkilic
commented
Dec 16, 2025

Copy link


Copy Markdown

Contributor
Hi @ItsYash1421, thank you for opening this PR! 🙏
There seems to be a bit of confusion here. There are two different redirect URL systems:
  1. Supabase Auth Login Redirects - Where to send YOUR users after they log into your app using Supabase Auth, allowed list is config.URIAllowListMap
  2. OAuth Client Redirect URIs - Where to send users when a THIRD-PARTY app uses Supabase Auth as their OAuth provider. This is what issue OAuth Dynamic Client Registration rejects custom URI schemes (inconsistency with PR #711) #2285 is about and it shouldn't be related to config.URIAllowListMap at all.
Closing this PR in favor of #2298, but really appreciate you taking the time to help!
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@depthfirst-appdepthfirst-app[bot]depthfirst-app[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@ItsYash1421@cemalkilic@YashKumarMeena001

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
fix: allow custom URI schemes in OAuth Dynamic Client Registration by ItsYash1421 · Pull Request #2286 · supabase/auth · GitHub
Skip to content
fix: allow custom URI schemes in OAuth Dynamic Client Registration - #2286
Closed
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Closed
fix: allow custom URI schemes in OAuth Dynamic Client Registration#2286
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Conversation
@ItsYash1421
@ItsYash1421ItsYash1421
commented
Dec 9, 2025

Copy link


Copy Markdown

What kind of change does this PR introduce?
Bug fix - Fixes OAuth Dynamic Client Registration to support custom URI schemes
What is the current behavior?
Issue:#2285
The OAuth 2.0 Dynamic Client Registration endpoint (POST /oauth/clients/register) rejects custom URI schemes (e.g., cursor://, exp://, myapp://) even when they are explicitly whitelisted in the additional_redirect_urls configuration or GOTRUE_URI_ALLOW_LIST environment variable.
Current Error
{
"code": 400,
"error_code": "validation_failed",
"msg": "400: invalid redirect_uri 'cursor://anysphere.cursor-mcp/callback': scheme must be HTTPS or HTTP (localhost only)"
}
Root Cause
The OAuth server's client registration logic uses strict validation that only allows http and https schemes, which is inconsistent with PR #711 that relaxed this validation for general auth flows to support native applications.
What is the new behavior?
The OAuth server now uses the same allow-list-based validation as the rest of the auth system (introduced in PR #711). Custom URI schemes work when explicitly configured in the allow list.
Test Results
All validation tests pass successfully:
![Test Results]
Screenshot 2025-12-09 at 12 06 06 PM
Screenshot 2025-12-09 at 12 06 27 PM
Screenshot 2025-12-09 at 12 06 45 PM
PASS: TestValidateRequestOrigin (9 test cases)
PASS: TestValidateRequestOriginEdgeCases (5 test cases)
PASS: TestInferClientTypeFromAuthMethod (5 test cases)
PASS: TestGetValidAuthMethodsForClientType (4 test cases)
PASS: TestValidateClientTypeConsistency (8 test cases)
PASS: TestDetermineClientType (7 test cases)
PASS: TestIsValidAuthMethodForClientType (7 test cases)
PASS: TestValidateClientAuthentication (5 test cases)
PASS: TestGetAllValidAuthMethods
Total: 8 test suites, 40+ test cases - ALL PASS 
Additional context
Changes Made
Files Modified:
  1. internal/api/oauthserver/service.go (~40 lines)
    • Changed validateRedirectURI() to use utilities.IsRedirectURLValid()
    • Updated validation methods to be Server methods for config access
    • Modified validate() methods to accept *Server parameter
  2. internal/api/oauthserver/service_test.go (~80 lines)
    • Updated TestRedirectURIValidation() to use new method signature
    • Added comprehensive TestCustomURISchemes() test
    • Updated SetupTest() to configure test URIs
References
@ItsYash1421
ItsYash1421
requested a review
from a team
as a code ownerDecember 9, 2025 06:59
depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

@cemalkilic
cemalkilic
commented
Dec 16, 2025

Copy link


Copy Markdown

Contributor
Hi @ItsYash1421, thank you for opening this PR! 🙏
There seems to be a bit of confusion here. There are two different redirect URL systems:
  1. Supabase Auth Login Redirects - Where to send YOUR users after they log into your app using Supabase Auth, allowed list is config.URIAllowListMap
  2. OAuth Client Redirect URIs - Where to send users when a THIRD-PARTY app uses Supabase Auth as their OAuth provider. This is what issue OAuth Dynamic Client Registration rejects custom URI schemes (inconsistency with PR #711) #2285 is about and it shouldn't be related to config.URIAllowListMap at all.
Closing this PR in favor of #2298, but really appreciate you taking the time to help!
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@depthfirst-appdepthfirst-app[bot]depthfirst-app[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@ItsYash1421@cemalkilic@YashKumarMeena001

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
fix: allow custom URI schemes in OAuth Dynamic Client Registration by ItsYash1421 · Pull Request #2286 · supabase/auth · GitHub
Skip to content
fix: allow custom URI schemes in OAuth Dynamic Client Registration - #2286
Closed
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Closed
fix: allow custom URI schemes in OAuth Dynamic Client Registration#2286
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Conversation
@ItsYash1421
@ItsYash1421ItsYash1421
commented
Dec 9, 2025

Copy link


Copy Markdown

What kind of change does this PR introduce?
Bug fix - Fixes OAuth Dynamic Client Registration to support custom URI schemes
What is the current behavior?
Issue:#2285
The OAuth 2.0 Dynamic Client Registration endpoint (POST /oauth/clients/register) rejects custom URI schemes (e.g., cursor://, exp://, myapp://) even when they are explicitly whitelisted in the additional_redirect_urls configuration or GOTRUE_URI_ALLOW_LIST environment variable.
Current Error
{
"code": 400,
"error_code": "validation_failed",
"msg": "400: invalid redirect_uri 'cursor://anysphere.cursor-mcp/callback': scheme must be HTTPS or HTTP (localhost only)"
}
Root Cause
The OAuth server's client registration logic uses strict validation that only allows http and https schemes, which is inconsistent with PR #711 that relaxed this validation for general auth flows to support native applications.
What is the new behavior?
The OAuth server now uses the same allow-list-based validation as the rest of the auth system (introduced in PR #711). Custom URI schemes work when explicitly configured in the allow list.
Test Results
All validation tests pass successfully:
![Test Results]
Screenshot 2025-12-09 at 12 06 06 PM
Screenshot 2025-12-09 at 12 06 27 PM
Screenshot 2025-12-09 at 12 06 45 PM
PASS: TestValidateRequestOrigin (9 test cases)
PASS: TestValidateRequestOriginEdgeCases (5 test cases)
PASS: TestInferClientTypeFromAuthMethod (5 test cases)
PASS: TestGetValidAuthMethodsForClientType (4 test cases)
PASS: TestValidateClientTypeConsistency (8 test cases)
PASS: TestDetermineClientType (7 test cases)
PASS: TestIsValidAuthMethodForClientType (7 test cases)
PASS: TestValidateClientAuthentication (5 test cases)
PASS: TestGetAllValidAuthMethods
Total: 8 test suites, 40+ test cases - ALL PASS 
Additional context
Changes Made
Files Modified:
  1. internal/api/oauthserver/service.go (~40 lines)
    • Changed validateRedirectURI() to use utilities.IsRedirectURLValid()
    • Updated validation methods to be Server methods for config access
    • Modified validate() methods to accept *Server parameter
  2. internal/api/oauthserver/service_test.go (~80 lines)
    • Updated TestRedirectURIValidation() to use new method signature
    • Added comprehensive TestCustomURISchemes() test
    • Updated SetupTest() to configure test URIs
References
@ItsYash1421
ItsYash1421
requested a review
from a team
as a code ownerDecember 9, 2025 06:59
depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

@cemalkilic
cemalkilic
commented
Dec 16, 2025

Copy link


Copy Markdown

Contributor
Hi @ItsYash1421, thank you for opening this PR! 🙏
There seems to be a bit of confusion here. There are two different redirect URL systems:
  1. Supabase Auth Login Redirects - Where to send YOUR users after they log into your app using Supabase Auth, allowed list is config.URIAllowListMap
  2. OAuth Client Redirect URIs - Where to send users when a THIRD-PARTY app uses Supabase Auth as their OAuth provider. This is what issue OAuth Dynamic Client Registration rejects custom URI schemes (inconsistency with PR #711) #2285 is about and it shouldn't be related to config.URIAllowListMap at all.
Closing this PR in favor of #2298, but really appreciate you taking the time to help!
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@depthfirst-appdepthfirst-app[bot]depthfirst-app[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@ItsYash1421@cemalkilic@YashKumarMeena001

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
fix: allow custom URI schemes in OAuth Dynamic Client Registration by ItsYash1421 · Pull Request #2286 · supabase/auth · GitHub
Skip to content
fix: allow custom URI schemes in OAuth Dynamic Client Registration - #2286
Closed
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Closed
fix: allow custom URI schemes in OAuth Dynamic Client Registration#2286
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Conversation
@ItsYash1421
@ItsYash1421ItsYash1421
commented
Dec 9, 2025

Copy link


Copy Markdown

What kind of change does this PR introduce?
Bug fix - Fixes OAuth Dynamic Client Registration to support custom URI schemes
What is the current behavior?
Issue:#2285
The OAuth 2.0 Dynamic Client Registration endpoint (POST /oauth/clients/register) rejects custom URI schemes (e.g., cursor://, exp://, myapp://) even when they are explicitly whitelisted in the additional_redirect_urls configuration or GOTRUE_URI_ALLOW_LIST environment variable.
Current Error
{
"code": 400,
"error_code": "validation_failed",
"msg": "400: invalid redirect_uri 'cursor://anysphere.cursor-mcp/callback': scheme must be HTTPS or HTTP (localhost only)"
}
Root Cause
The OAuth server's client registration logic uses strict validation that only allows http and https schemes, which is inconsistent with PR #711 that relaxed this validation for general auth flows to support native applications.
What is the new behavior?
The OAuth server now uses the same allow-list-based validation as the rest of the auth system (introduced in PR #711). Custom URI schemes work when explicitly configured in the allow list.
Test Results
All validation tests pass successfully:
![Test Results]
Screenshot 2025-12-09 at 12 06 06 PM
Screenshot 2025-12-09 at 12 06 27 PM
Screenshot 2025-12-09 at 12 06 45 PM
PASS: TestValidateRequestOrigin (9 test cases)
PASS: TestValidateRequestOriginEdgeCases (5 test cases)
PASS: TestInferClientTypeFromAuthMethod (5 test cases)
PASS: TestGetValidAuthMethodsForClientType (4 test cases)
PASS: TestValidateClientTypeConsistency (8 test cases)
PASS: TestDetermineClientType (7 test cases)
PASS: TestIsValidAuthMethodForClientType (7 test cases)
PASS: TestValidateClientAuthentication (5 test cases)
PASS: TestGetAllValidAuthMethods
Total: 8 test suites, 40+ test cases - ALL PASS 
Additional context
Changes Made
Files Modified:
  1. internal/api/oauthserver/service.go (~40 lines)
    • Changed validateRedirectURI() to use utilities.IsRedirectURLValid()
    • Updated validation methods to be Server methods for config access
    • Modified validate() methods to accept *Server parameter
  2. internal/api/oauthserver/service_test.go (~80 lines)
    • Updated TestRedirectURIValidation() to use new method signature
    • Added comprehensive TestCustomURISchemes() test
    • Updated SetupTest() to configure test URIs
References
@ItsYash1421
ItsYash1421
requested a review
from a team
as a code ownerDecember 9, 2025 06:59
depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

@cemalkilic
cemalkilic
commented
Dec 16, 2025

Copy link


Copy Markdown

Contributor
Hi @ItsYash1421, thank you for opening this PR! 🙏
There seems to be a bit of confusion here. There are two different redirect URL systems:
  1. Supabase Auth Login Redirects - Where to send YOUR users after they log into your app using Supabase Auth, allowed list is config.URIAllowListMap
  2. OAuth Client Redirect URIs - Where to send users when a THIRD-PARTY app uses Supabase Auth as their OAuth provider. This is what issue OAuth Dynamic Client Registration rejects custom URI schemes (inconsistency with PR #711) #2285 is about and it shouldn't be related to config.URIAllowListMap at all.
Closing this PR in favor of #2298, but really appreciate you taking the time to help!
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@depthfirst-appdepthfirst-app[bot]depthfirst-app[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@ItsYash1421@cemalkilic@YashKumarMeena001

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
fix: allow custom URI schemes in OAuth Dynamic Client Registration by ItsYash1421 · Pull Request #2286 · supabase/auth · GitHub
Skip to content
fix: allow custom URI schemes in OAuth Dynamic Client Registration - #2286
Closed
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Closed
fix: allow custom URI schemes in OAuth Dynamic Client Registration#2286
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Conversation
@ItsYash1421
@ItsYash1421ItsYash1421
commented
Dec 9, 2025

Copy link


Copy Markdown

What kind of change does this PR introduce?
Bug fix - Fixes OAuth Dynamic Client Registration to support custom URI schemes
What is the current behavior?
Issue:#2285
The OAuth 2.0 Dynamic Client Registration endpoint (POST /oauth/clients/register) rejects custom URI schemes (e.g., cursor://, exp://, myapp://) even when they are explicitly whitelisted in the additional_redirect_urls configuration or GOTRUE_URI_ALLOW_LIST environment variable.
Current Error
{
"code": 400,
"error_code": "validation_failed",
"msg": "400: invalid redirect_uri 'cursor://anysphere.cursor-mcp/callback': scheme must be HTTPS or HTTP (localhost only)"
}
Root Cause
The OAuth server's client registration logic uses strict validation that only allows http and https schemes, which is inconsistent with PR #711 that relaxed this validation for general auth flows to support native applications.
What is the new behavior?
The OAuth server now uses the same allow-list-based validation as the rest of the auth system (introduced in PR #711). Custom URI schemes work when explicitly configured in the allow list.
Test Results
All validation tests pass successfully:
![Test Results]
Screenshot 2025-12-09 at 12 06 06 PM
Screenshot 2025-12-09 at 12 06 27 PM
Screenshot 2025-12-09 at 12 06 45 PM
PASS: TestValidateRequestOrigin (9 test cases)
PASS: TestValidateRequestOriginEdgeCases (5 test cases)
PASS: TestInferClientTypeFromAuthMethod (5 test cases)
PASS: TestGetValidAuthMethodsForClientType (4 test cases)
PASS: TestValidateClientTypeConsistency (8 test cases)
PASS: TestDetermineClientType (7 test cases)
PASS: TestIsValidAuthMethodForClientType (7 test cases)
PASS: TestValidateClientAuthentication (5 test cases)
PASS: TestGetAllValidAuthMethods
Total: 8 test suites, 40+ test cases - ALL PASS 
Additional context
Changes Made
Files Modified:
  1. internal/api/oauthserver/service.go (~40 lines)
    • Changed validateRedirectURI() to use utilities.IsRedirectURLValid()
    • Updated validation methods to be Server methods for config access
    • Modified validate() methods to accept *Server parameter
  2. internal/api/oauthserver/service_test.go (~80 lines)
    • Updated TestRedirectURIValidation() to use new method signature
    • Added comprehensive TestCustomURISchemes() test
    • Updated SetupTest() to configure test URIs
References
@ItsYash1421
ItsYash1421
requested a review
from a team
as a code ownerDecember 9, 2025 06:59
depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

@cemalkilic
cemalkilic
commented
Dec 16, 2025

Copy link


Copy Markdown

Contributor
Hi @ItsYash1421, thank you for opening this PR! 🙏
There seems to be a bit of confusion here. There are two different redirect URL systems:
  1. Supabase Auth Login Redirects - Where to send YOUR users after they log into your app using Supabase Auth, allowed list is config.URIAllowListMap
  2. OAuth Client Redirect URIs - Where to send users when a THIRD-PARTY app uses Supabase Auth as their OAuth provider. This is what issue OAuth Dynamic Client Registration rejects custom URI schemes (inconsistency with PR #711) #2285 is about and it shouldn't be related to config.URIAllowListMap at all.
Closing this PR in favor of #2298, but really appreciate you taking the time to help!
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@depthfirst-appdepthfirst-app[bot]depthfirst-app[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@ItsYash1421@cemalkilic@YashKumarMeena001

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
fix: allow custom URI schemes in OAuth Dynamic Client Registration by ItsYash1421 · Pull Request #2286 · supabase/auth · GitHub
Skip to content
fix: allow custom URI schemes in OAuth Dynamic Client Registration - #2286
Closed
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Closed
fix: allow custom URI schemes in OAuth Dynamic Client Registration#2286
ItsYash1421 wants to merge 8 commits into
supabase:masterfrom 
ItsYash1421:fix/oauth-custom-uri-schemes
Conversation
@ItsYash1421
@ItsYash1421ItsYash1421
commented
Dec 9, 2025

Copy link


Copy Markdown

What kind of change does this PR introduce?
Bug fix - Fixes OAuth Dynamic Client Registration to support custom URI schemes
What is the current behavior?
Issue:#2285
The OAuth 2.0 Dynamic Client Registration endpoint (POST /oauth/clients/register) rejects custom URI schemes (e.g., cursor://, exp://, myapp://) even when they are explicitly whitelisted in the additional_redirect_urls configuration or GOTRUE_URI_ALLOW_LIST environment variable.
Current Error
{
"code": 400,
"error_code": "validation_failed",
"msg": "400: invalid redirect_uri 'cursor://anysphere.cursor-mcp/callback': scheme must be HTTPS or HTTP (localhost only)"
}
Root Cause
The OAuth server's client registration logic uses strict validation that only allows http and https schemes, which is inconsistent with PR #711 that relaxed this validation for general auth flows to support native applications.
What is the new behavior?
The OAuth server now uses the same allow-list-based validation as the rest of the auth system (introduced in PR #711). Custom URI schemes work when explicitly configured in the allow list.
Test Results
All validation tests pass successfully:
![Test Results]
Screenshot 2025-12-09 at 12 06 06 PM
Screenshot 2025-12-09 at 12 06 27 PM
Screenshot 2025-12-09 at 12 06 45 PM
PASS: TestValidateRequestOrigin (9 test cases)
PASS: TestValidateRequestOriginEdgeCases (5 test cases)
PASS: TestInferClientTypeFromAuthMethod (5 test cases)
PASS: TestGetValidAuthMethodsForClientType (4 test cases)
PASS: TestValidateClientTypeConsistency (8 test cases)
PASS: TestDetermineClientType (7 test cases)
PASS: TestIsValidAuthMethodForClientType (7 test cases)
PASS: TestValidateClientAuthentication (5 test cases)
PASS: TestGetAllValidAuthMethods
Total: 8 test suites, 40+ test cases - ALL PASS 
Additional context
Changes Made
Files Modified:
  1. internal/api/oauthserver/service.go (~40 lines)
    • Changed validateRedirectURI() to use utilities.IsRedirectURLValid()
    • Updated validation methods to be Server methods for config access
    • Modified validate() methods to accept *Server parameter
  2. internal/api/oauthserver/service_test.go (~80 lines)
    • Updated TestRedirectURIValidation() to use new method signature
    • Added comprehensive TestCustomURISchemes() test
    • Updated SetupTest() to configure test URIs
References
@ItsYash1421
ItsYash1421
requested a review
from a team
as a code ownerDecember 9, 2025 06:59
depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

depthfirst-app[bot]
depthfirst-appBot
reviewed
Dec 9, 2025
View reviewed changes
Comment threadinternal/api/oauthserver/service.go
Outdated

@cemalkilic
cemalkilic
commented
Dec 16, 2025

Copy link


Copy Markdown

Contributor
Hi @ItsYash1421, thank you for opening this PR! 🙏
There seems to be a bit of confusion here. There are two different redirect URL systems:
  1. Supabase Auth Login Redirects - Where to send YOUR users after they log into your app using Supabase Auth, allowed list is config.URIAllowListMap
  2. OAuth Client Redirect URIs - Where to send users when a THIRD-PARTY app uses Supabase Auth as their OAuth provider. This is what issue OAuth Dynamic Client Registration rejects custom URI schemes (inconsistency with PR #711) #2285 is about and it shouldn't be related to config.URIAllowListMap at all.
Closing this PR in favor of #2298, but really appreciate you taking the time to help!
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@depthfirst-appdepthfirst-app[bot]depthfirst-app[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@ItsYash1421@cemalkilic@YashKumarMeena001