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

[management] Swagger import should guarantee uniqueness of endpoint group / endpoint name #1685

Closed
gs11 opened this Issue Nov 20, 2018 · 0 comments

Comments

Projects
None yet
4 participants
@gs11

gs11 commented Nov 20, 2018

Expected Behavior

Creating API from swagger should ensure endpoint group / endpoint name uniqueness.
See related #1578

Current Behavior

Both endpoint group & endpoint is named "default" which causes policies to fail later on due to duplicate key errors.

Possible Solution

Group should be named as they're done when creating API from scratch.

Steps to Reproduce (for bugs)

  1. Import Swagger and complete configuration with backend.
  2. Set up JWT plan
  3. Execute API call with any token and get 500 internal error

Context

JWT plans not functional per default, need manual renaming of group or endpoint.

Your Environment

  • Version used: 1.20.6
  • Browser Name and version: n/a
  • Operating System and version: n/a

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Nov 20, 2018

@brasseld brasseld changed the title from Swagger import should guarantee uniqueness of endpoint group / endpoint name to [management] Swagger import should guarantee uniqueness of endpoint group / endpoint name Nov 20, 2018

@brasseld brasseld self-assigned this Nov 20, 2018

@brasseld brasseld added the type: bug label Nov 20, 2018

@NicolasGeraud NicolasGeraud added this to the 1.20.7 milestone Nov 23, 2018

aelamrani added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Nov 29, 2018

aelamrani added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Dec 5, 2018

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