@zuplo/lint-win32-x64 7.7.16 → 7.7.17
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.
|
@@ -3662,7 +3662,7 @@
|
|
|
3662
3662
|
},
|
|
3663
3663
|
"clientSecret": {
|
|
3664
3664
|
"type": "string",
|
|
3665
|
-
"examples": ["$env(
|
|
3665
|
+
"examples": ["$env(AUTH0_CLIENT_SECRET)"],
|
|
3666
3666
|
"description": "The Auth0 client_secret. Use $env(...) to source from a secret environment variable."
|
|
3667
3667
|
},
|
|
3668
3668
|
"scope": {
|
|
@@ -5047,7 +5047,7 @@
|
|
|
5047
5047
|
"examples": [
|
|
5048
5048
|
"https://my-tenant.us.auth0.com/authorize"
|
|
5049
5049
|
],
|
|
5050
|
-
"description": "The IdP /authorize endpoint to redirect the user to. For local development on loopback, use http://127.0.0.1:9000/oauth/dev-login."
|
|
5050
|
+
"description": "The IdP /authorize endpoint to redirect the user to. For local development on loopback, use http://127.0.0.1:9000/__zuplo/oauth/dev-login (the gateway's default basePath is /__zuplo; adjust if the plugin is configured with a different one)."
|
|
5051
5051
|
},
|
|
5052
5052
|
"tokenUrl": {
|
|
5053
5053
|
"type": "string",
|
|
@@ -5805,6 +5805,9 @@
|
|
|
5805
5805
|
{
|
|
5806
5806
|
"required": ["prompt"]
|
|
5807
5807
|
},
|
|
5808
|
+
{
|
|
5809
|
+
"required": ["skipIssuerMetadataValidation"]
|
|
5810
|
+
},
|
|
5808
5811
|
{
|
|
5809
5812
|
"required": ["clientRegistration"]
|
|
5810
5813
|
}
|
|
@@ -5874,6 +5877,11 @@
|
|
|
5874
5877
|
}
|
|
5875
5878
|
]
|
|
5876
5879
|
},
|
|
5880
|
+
"skipIssuerMetadataValidation": {
|
|
5881
|
+
"type": "boolean",
|
|
5882
|
+
"x-advanced": true,
|
|
5883
|
+
"description": "Skips the RFC 8414 section 3.3 issuer-echo check when discovering the upstream authorization server. That check requires the `issuer` in the authorization server's metadata to equal the `authorization_servers` entry the protected-resource metadata advertised. Some providers publish a path-scoped authorization server whose metadata reports the root origin instead — for example ServiceNow advertises `https://<instance>.service-now.com/sncapps/...` but its metadata reports `https://<instance>.service-now.com` — so discovery hard-fails without this option. Warning: enabling this puts the connection out of spec. The check is an unqualified MUST in both RFC 8414 section 3.3 and the MCP authorization spec, which require rejecting a metadata document whose `issuer` differs from the identifier the well-known URL was built from; the spec's own example is a document served from `https://attacker.example/.well-known/oauth-authorization-server` claiming `\"issuer\": \"https://honest.example\"`. The echo check binds the metadata to the TLS-authenticated host it came from, and with it off the gateway trusts the authorization, token and JWKS endpoints from a document that never proved it speaks for that issuer. Only enable it for a specific upstream known to publish a mismatched issuer, and only when the metadata URL's host is itself trusted. It relaxes the discovery-time check only — the RFC 9207 authorization-response check and the callback-leg authorization-server binding still apply."
|
|
5884
|
+
},
|
|
5877
5885
|
"clientRegistration": {
|
|
5878
5886
|
"x-advanced": true,
|
|
5879
5887
|
"description": "OAuth client registration mode. Defaults to `auto`, which uses Client ID Metadata Documents when the upstream advertises support and falls back to Dynamic Client Registration otherwise.",
|
package/bin/version.txt
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
7.7.
|
|
1
|
+
7.7.17
|