Revamp Developer Portal: add: Configure CORS how-to guide and CORS troubleshooting page#1950
Open
sharadregoti wants to merge 14 commits intoportal-ia-structural-changes-a3-a7from
Open
Revamp Developer Portal: add: Configure CORS how-to guide and CORS troubleshooting page#1950sharadregoti wants to merge 14 commits intoportal-ia-structural-changes-a3-a7from
sharadregoti wants to merge 14 commits intoportal-ia-structural-changes-a3-a7from
Conversation
…ing page - configure-cors.mdx: covers Portal application CORS (env vars + Helm) and Gateway CORS for Classic and OAS API definitions; includes TT-15960 regression callout and AllowedOrigins default TODO - cors-issues.mdx: troubleshooting page with four validated scenarios (Portal CORS disabled, Gateway CORS misconfigured, TT-15960 403 regression, credentials+wildcard conflict) based on OEL code analysis and customer-insights Zendesk cases
|
Failed to generate code suggestions for PR |
sharadregoti
changed the title
- Remove Tyk Classic API definition section; replace with a Note callout linking to the Classic CORS reference - Promote Tyk OAS as the sole primary path for Gateway CORS config - Convert bold-prefixed pseudo-steps to proper numbered list items with continuation content indented under each step - Replace env var column in optional settings table with config keys (CORS.MaxAge, CORS.AllowCredentials) linked to their exact anchors in the configuration reference; remove PORTAL_CORS_DEBUG (not in config reference); correct default allowed methods to GET and POST
- Replace Kubernetes (Helm) tabs with Config file (JSON) tabs on all three Portal CORS steps - Link PORTAL_CORS_ENABLE and PORTAL_CORS_ALLOWED_ORIGINS to their exact anchors in the configuration reference wherever they appear in prose and warning callouts - Remove Type column from optional settings table
…hnologies/tyk-docs into portal-b20-configure-cors
…hnologies/tyk-docs into portal-b20-configure-cors
OEL confirmed: rs/cors v1.11.1 treats an empty AllowedOrigins slice as allow-all (sets allowedOriginsAll=true). When PORTAL_CORS_ALLOWED_ORIGINS is unset the Portal allows all origins — not "no origins" as previously stated. Update both B20 and configuration.mdx to reflect actual behavior.
…hnologies/tyk-docs into portal-b20-configure-cors
- Add sidebarTitle and keywords to frontmatter - Link PORTAL_CORS_ENABLE, PORTAL_CORS_ALLOW_CREDENTIALS, and PORTAL_CORS_ALLOWED_ORIGINS in prose to their config reference anchors - Replace em-dashes in all four accordion titles with restructured phrasing
…hnologies/tyk-docs into portal-b20-configure-cors
sharadregoti
commented
May 1, 2026
sharadregoti
commented
May 1, 2026
Co-authored-by: Master <sharadregoti15@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
portal/how-to-guides/configure-cors.mdx): New how-to guide covering both CORS layers — Portal application CORS (7 env vars, env var + Helm tabs) and Gateway CORS per API definition (Classic and Tyk OAS). Includes TT-15960 regression callout and a TODO comment on the AllowedOrigins default discrepancy (pending confirmation from Portal team).portal/troubleshooting/cors-issues.mdx): New troubleshooting page with four validated CORS error scenarios in AccordionGroup format, covering Portal CORS disabled, Gateway CORS misconfigured, TT-15960403regression, and credentials+wildcard origin conflict. Scenarios validated via OEL code analysis and confirmed against customer-insights Zendesk cases (Centerpoint Connect, International SOS).🤖 Generated with Claude Code