How should I implement a user-defined APIKey verification mode
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description
We want to generate a custom API Key for end users and verify API permissions when requesting the API through wso2.
We implement the KeyValidationHandler class and place the generated plug-in jar in repository/components/lib and lib directories. We also configure the key_managent validation method as the plug-in class. The logic for validating the APIKey is not executed when requesting the wso2 API. How should I correctly write the custom APIKey validation logic?
Affected Component
Analytics
Version
4.4.0
Environment Details (with versions)
Ubuntu 22.04.5 LTS
Related Issues
No response
Suggested Labels
No response
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 reported KeyValidationHandler implementation and the configured key_managent validation method, then verify how the generated plug-in JAR is placed in repository/components/lib and lib. Determine why the custom APIKey validation logic is not invoked for WSO2 API requests; done means the correct configuration and validation flow are documented for API Management 4.4.0.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, authorization, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100