-
Notifications
You must be signed in to change notification settings - Fork 16
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
Pass HTTP auth secrets using v2 manifest format #203
Conversation
HYP-1207 Host authentication needs serious improvement
Currently we support a single "API Key" for each host. We allow the user to enter it in the console, we save it to Secrets Manager, and we assign it to a header on outbound requests where the header is specified by This is very limiting, as there are many different kinds of authentication schemes used by APIs. Many APIs pass tokens on the url query string, or in the request body, or other locations. Some require more complex short-lived tokens to be generated on the fly, etc. Even with the current approach it's not ideal for the user because they have to include the entire header - not just their auth token. For example, if using GitHub API, if your token is For APIs that use HTTP Basic authentication, they need a username and password - both of which should be secret. We then have to compose the APIs that require short-lived JWTs may need some support for generating them based on other credentials (private keys, etc.) We should break this out into several items to support each auth scheme, and work from the user backwards. ie., start from the function, through to the runtime, then the manifest, and ultimately the console. |
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Completes HYP-1207