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

Allow x-consumer-* headers for internal audience #594

Closed
2 tasks done
rbarilani opened this issue Jul 21, 2020 · 0 comments
Closed
2 tasks done

Allow x-consumer-* headers for internal audience #594

rbarilani opened this issue Jul 21, 2020 · 0 comments
Assignees

Comments

@rbarilani
Copy link

rbarilani commented Jul 21, 2020

Following the discussion on API Guild JF - 2020-07-14, we want to allow x-consumer headers to be specified in Open API specification.

related to #554

The X-Consumer headers to whitelist are:

X-Consumer: contains a base64 JSON payload identifying the zDirect API or UI consumer (user or OAuth2 client)
X-Consumer-Signature: contains signature to verify the X-Consumer payload
X-Consumer-Key-ID: contains the key identifier to retrieve the public key to verify the X-Consumer-Signature

Acceptance Criteria

  • Zally MUST allow the mentioned headers to be specified in OpenAPI specification
  • The headers and their description SHOULD be added to the guidelines
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

4 participants