@mcpfn/auth 0.0.3 → 0.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +19 -0
- package/dist/index.cjs +5966 -171
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +14 -1
- package/dist/index.d.ts +14 -1
- package/dist/index.js +5964 -170
- package/dist/index.js.map +1 -1
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -43,6 +43,25 @@ Pass it to `streamableHttpTarget`. Complete interactive authorization with
|
|
|
43
43
|
fails before token exchange. Dynamic loopback ports are accepted only when the
|
|
44
44
|
registered URI omits the port. Other redirect URIs require exact equality.
|
|
45
45
|
|
|
46
|
+
Native private-use redirects use RFC 8252's reverse-domain scheme policy by
|
|
47
|
+
default, accepting values such as `com.example.app:/oauth/callback`. Hosts can
|
|
48
|
+
set `redirectPolicy.privateUseSchemePolicy: "disabled"` to reject all native
|
|
49
|
+
schemes, or opt into `"compatible"` for well-formed non-web schemes used by
|
|
50
|
+
native clients and name those schemes explicitly, for example
|
|
51
|
+
`compatiblePrivateUseSchemes: ["cursor"]` for
|
|
52
|
+
`cursor://anysphere.cursor-mcp/oauth/callback`. Compatibility mode still rejects
|
|
53
|
+
web, network, launcher, and dangerous schemes, non-loopback HTTP, credentials,
|
|
54
|
+
fragments, wildcards, and malformed or opaque callbacks. Authorization always
|
|
55
|
+
requires exact matching; dynamic-port matching remains restricted to loopback
|
|
56
|
+
HTTP. Successful dynamic
|
|
57
|
+
registrations expose compatibility scheme names and counts through the hosted
|
|
58
|
+
authorization diagnostics hook so hosts can audit use without recording callback
|
|
59
|
+
queries.
|
|
60
|
+
|
|
61
|
+
The deprecated `allowPrivateUseSchemes` boolean remains accepted for 0.0.3
|
|
62
|
+
callers: `false` maps to `disabled` and `true` maps to `rfc8252`. When neither
|
|
63
|
+
field is provided, 0.0.4 defaults to `rfc8252`.
|
|
64
|
+
|
|
46
65
|
## Hosted compatibility
|
|
47
66
|
|
|
48
67
|
`createMcpAuthorizationCompatibilityHandler()` publishes authorization-server
|