🔄 Preview: [TT-16039] Added Upstream OAuth Auth Method - #2769
Draft
probelabs[bot] wants to merge 479 commits into
Draft
🔄 Preview: [TT-16039] Added Upstream OAuth Auth Method#2769probelabs[bot] wants to merge 479 commits into
probelabs[bot] wants to merge 479 commits into
probelabs / Visor: security
failed
Aug 21, 2026 in 31s
🚨 Check Failed
security check failed because fail_if condition was met.
Details
📊 Summary
- Total Issues: 2
- Error Issues: 2
🔍 Failure Condition Results
Failed Conditions
- global_fail_if: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
- Severity: ❌ error
Issues by Category
Security (1)
- ❌ api-management/upstream-authentication/oauth.mdx:70 - Documentation examples for
tokenUrlusehttp://which is insecure for transmitting credentials. This could lead users to configure unencrypted connections to their authorization server, exposing sensitive data like client secrets or passwords. All authentication-related communication must occur over TLS (https://).
Logic (1)
- ❌ system:0 - Global failure condition met: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check failure on line 250 in api-management/upstream-authentication/oauth.mdx
probelabs / Visor: security
security Issue
Documentation examples for `tokenUrl` use `http://` which is insecure for transmitting credentials. This could lead users to configure unencrypted connections to their authorization server, exposing sensitive data like client secrets or passwords. All authentication-related communication must occur over TLS (`https://`).
Raw output
Replace all instances of `http://<my-auth-server>/token` with `https://<my-auth-server>/token` in the documentation examples and explanatory text to promote secure-by-default configurations.
Loading