wso2 / wso2/api-platform

[Bug]: After Subscribe Try Out(Documentation) should show "Subscription-Key" header information

Open
#2,941 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect/API Severity/Major Type/Bug
Dominant language
Go
Stars
71
Forks
111
Avg merge
1d 14h
Merged PRs (30d)
110

Description

Please select the area the issue is related to

Developer Portal

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)

Description

After Subscribe Try Out(Documentation) should show "Subscription-Key" header information

Image

Also when I try out the curl it's not working,

curl --request GET
--url https://localhost:9543/default/views/default/api/catalog-api-v1.0/tryout-proxy/http://localhost:8080/catalog/products
--header 'Accept: application/json'
--header 'X-API-Key: Mg4__RSjbEMLYe_Y5HbkpeCaV_na5vYD_r43HF9_apI'
--header 'Subscription-Key: fc75e83d6925d23444ce115f8c12b92b0903e8fb58b98d12011d3bd5e284fd97' -k
{"error":"forbidden","message":"Request origin is not allowed."}

Steps to Reproduce

Subscribe to API
Navigate to Documentation to invoke the API

Severity Level of the Issue

Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)

Environment Details (with versions)

Devportal 1.0.0-Beta

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Subscribe to API and Documentation try-out flow in Devportal 1.0.0-Beta, then inspect the generated curl request and its forbidden response. Done means the try-out documentation shows the Subscription-Key header and the generated request succeeds without the origin error.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.