Fix #3499: Restrict endpoint security type to only available ones #12829
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.
Purpose
This PR addresses a validation gap in the Publisher REST API, where custom endpoint security types could be added through API creation, even if they were not part of the predefined set of supported security types.
Previously, there was no restriction on the endpoint security type, allowing users to specify any arbitrary value.
The new implementation introduces validation in the validateEndpointSecurityType method to ensure that only supported security types—None, Basic, Digest, and OAuth—are allowed. If an invalid security type is detected, an appropriate error message is returned.
Related to
Issue: wso2/api-manager#3499