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

[gateway] Api Keys not recognized after migration to 1.11.x #938

Closed
brasseld opened this Issue Dec 9, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@brasseld
Member

brasseld commented Dec 9, 2017

When upgrading from 1.10.x to 1.11.x some api_keys and plan's subscriptions are no more recognized.

This is happening because some pretty old plans definition did not contain the security type.
For example:

db.plans.find({_id:"700fdb85-4acb-0e5f-42f1-4169d3c866b9"}) 
{ "_id" : "700fdb85-4acb-0e5f-42f1-4169d3c866b9" 
, "_class" : "io.gravitee.repository.mongodb.management.internal.model.PlanMongo" 
, "name" : "fid demat dev Plan" 
, "description" : "Default fid demat dev Plan" 
, "validation" : "AUTO" 
, "type" : "API" 
, "status" : "PUBLISHED" 
, "order" : 0 
, "apis" : [ "demat-fid" ] 
, "definition" : "{\"/\" : [ ]}" 
, "characteristics" : [ ] 
, "createdAt" : ISODate("2017-01-18T10:13:27.674Z") 
, "updatedAt" : ISODate("2017-01-18T10:13:27.674Z") }

And the security type is required by the underlying api-key refresher service.

@brasseld brasseld added the type: bug label Dec 9, 2017

@brasseld brasseld added this to the 1.12.0 milestone Dec 9, 2017

@brasseld brasseld self-assigned this Dec 9, 2017

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Dec 9, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-gateway that referenced this issue Dec 10, 2017

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