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

Add SSL enablement #38

Merged
merged 1 commit into from
May 5, 2018
Merged

Add SSL enablement #38

merged 1 commit into from
May 5, 2018

Conversation

chefsalim
Copy link
Contributor

This change adds instructions (and related script changes) for enabling SSL on the UI/API endpoints for the on-prem depot.

Signed-off-by: Salim Alam [email protected]

tenor-260598948

README.md Outdated

By default, the on-premise Builder will expose the web UI and API via http. Though it allows for easier setup and is fine for evaluation purposes, for a secure and more permanent installation it is recommended that you enable SSL on the Builder endpoints.

In order to do prepare for this, you should procure a SSL certificate. If needed, you may use a self-signed certificate - however if you do so, you will need to install the certificate in the trusted chain on client machines (ones that will use the Builder UI or APIs). You may use the `SSL_CERT_FILE` environment variable to also point to the certificate on client machines when invoking the `hab` client, for example:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strike the fourth word here, do.

Copy link
Contributor

@raskchanky raskchanky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One tiny grammatical typo, but otherwise looks great.

@raskchanky
Copy link
Contributor

Signed-off-by: Salim Alam <[email protected]>
@chefsalim chefsalim merged commit 92bf00e into master May 5, 2018
@chefsalim chefsalim deleted the SA/enable-ssl branch May 5, 2018 01:15
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

Successfully merging this pull request may close these issues.

2 participants