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

[policy] [api-key] Customize api-key header #444

Closed
Frintrop opened this Issue Feb 12, 2017 · 7 comments

Comments

Projects
None yet
3 participants
@Frintrop

Frintrop commented Feb 12, 2017

Is it possible to rename api key header X-Gravitee-Api-Key like X-Gravitee-Transaction-ID header?

@NicolasGeraud

This comment has been minimized.

Member

NicolasGeraud commented Feb 12, 2017

No,

but this could be a useful feature.

@Frintrop

This comment has been minimized.

Frintrop commented Feb 12, 2017

Yes. While migration from another thirdparty api management solution and keep all clients unchanged...!

@NicolasGeraud

This comment has been minimized.

Member

NicolasGeraud commented Feb 12, 2017

This is what you want to test with Gravitee.io ?

Please let us know, there 's a company behind Gravitee.io (https://graviteesource.com/) that could provide professional support.

@Frintrop

This comment has been minimized.

Frintrop commented Feb 12, 2017

Many thx. We have clients using X-API-KEY header now. if we can define our gravitee header ourself we don´t need to rewrite it with mod_rewrite ...

@Frintrop

This comment has been minimized.

Frintrop commented Feb 12, 2017

Maybe there is a workaround with transform-header-policy ?

@brasseld

This comment has been minimized.

Member

brasseld commented Feb 12, 2017

Unfortunately, there is no workaround using transform-header policy.

The reason for this is simple: when handling a request, three policy chains are executed:

  1. Security policy chain : security
  2. Plan policy chain : policies relative to the plan itself : rate-limit / quota, resource filtering, ...
  3. API policy chain : policies you are managing through the UI.

So, for sure, we have to implement a new feature to:

  1. Set a custom X-Api-Key header for all the APIs
  2. Be able to customize the X-Api-Key header on a per-api or per-plan basis.

@NicolasGeraud NicolasGeraud changed the title from Rename api key header to Customize api key header Feb 13, 2017

@brasseld brasseld changed the title from Customize api key header to [policy] [api-key] Customize api-key header Feb 16, 2017

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

brasseld added a commit to gravitee-io/gravitee-policy-apikey that referenced this issue Apr 18, 2017

@brasseld brasseld self-assigned this Apr 18, 2017

@brasseld

This comment has been minimized.

Member

brasseld commented Apr 18, 2017

This PR allows to set a custom Api key header / query parameter for all APIs / plans.

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

brasseld added a commit to gravitee-io/gravitee-policy-apikey that referenced this issue Apr 18, 2017

@brasseld brasseld added this to the 1.5.0 milestone Apr 18, 2017

NicolasGeraud added a commit to gravitee-io/gravitee-policy-apikey that referenced this issue Apr 19, 2017

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

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