Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to save resources for API #1949

Closed
dinithnirman opened this issue Jun 24, 2023 · 1 comment
Closed

Unable to save resources for API #1949

dinithnirman opened this issue Jun 24, 2023 · 1 comment

Comments

@dinithnirman
Copy link

Description

Hi Team

After performing an update of WSO2AM (WSO2 API Manager) version 4.1 from U2 level 70 to level 83, we have encountered an issue regarding the saving of changes made in the 'Resources' tab for any registered APIs. It has been observed that the changes made in this tab are not being saved successfully. However, it should be noted that the changes made to the sample PizzaShackAPI were successfully saved.

Analysis
We have identified that the issue happened to APIs without the "securitySchemes" tag. Since the sample API (PizzaShackAPI) contains the "securitySchemes" tag, it allows saving the 'Resources' changes.

We have setup this locally and are able to reproduce the issue. Please refer to the below update levels which we tested this issue.

  • wso2am-4.1.0 vanilla pack: Does not reproduce the issue and working fine
  • wso2am-4.1.0 level 83: Reproduced the issue
  • wso2am-4.1.0 level 85 (latest): Reproduced the issue

Steps to Reproduce

  • Get a updated wso2am-4.1.0 pack
  • Create an API (API should not have "securitySchemes" tag in the API definition)
  • Try to add Resources and save.
  • Changes won't save and you will be able to see the below error in the browser console.

error

Affected Component

APIM

Version

4.1.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

https://github.com/wso2-enterprise/wso2-apim-internal/issues/3522

Suggested Labels

Affected/APIM-4.1.0

@YasasRangika
Copy link

As mentioned in the linked internal ticket, this issue does not affect the master branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants