Missing notes on key manager profile deprecation
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
The key manager profile (api-key-manager) is deprecated from APIM 4.0.0 onwards as we are now moving on to JWTs after deprecating the Opaque tokens. Since the gateway is capable of validating the JWT tokens even if the control-plane is down, there is no requirement to run the key manager profile separately as a scalable one.
This information is missing from [1].
Profile deprecation is missing from [2] as well.
[1] - https://apim.docs.wso2.com/en/latest/install-and-setup/setup/distributed-deployment/product-profiles/#running-the-api-m-profiles
[2] - https://apim.docs.wso2.com/en/latest/get-started/about-this-release/#deprecated-features-and-functionalities
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked “Running the API-M Profiles” page and the “Deprecated Features and Functionalities” section in the release overview. Document that the api-key-manager profile is deprecated from APIM 4.0.0 and explain the JWT-based deployment context; done means both referenced pages contain this information.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100