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

Proposal: TLS Values #249

Open
ChrisTalman opened this issue Mar 30, 2020 · 0 comments
Open

Proposal: TLS Values #249

ChrisTalman opened this issue Mar 30, 2020 · 0 comments

Comments

@ChrisTalman
Copy link

redbird looks great.

For TLS, is it possible to provide raw certificate values instead of paths?

In my use case, the certificates are not stored in the file system. They could be stored there at runtime. The trouble is, this would require the files to be managed with additional code. It would be great if the raw certificate values could simply be provided directly to redbird.

If this is not currently possible, could it be implemented?

It may be possible to implement it in a non-breaking manner. Strings could continue to be treated as file paths. But, if an object is provided, it could be checked for one of two keys: either path, for a file path string, or value, for a raw certificate string.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant