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

Fixes #11363 - Smart proxy dynflow console auth #12

Merged
merged 1 commit into from Feb 16, 2016

Conversation

adamruzicka
Copy link
Contributor

Plain HTTP remains freely accessible, connections over HTTPS require a client SSL certificate

@iNecas
Copy link
Member

iNecas commented Feb 15, 2016

Thinking: maybe we should make the option configurable + the trusted host check (default to false, but useful for the http users).

@@ -1,3 +1,5 @@
---
:enabled: true
:database: /var/lib/foreman-proxy/dynflow/dynflow.sqlite
:dynflow_console_authorize_with_ssl_client: false
Copy link
Member

Choose a reason for hiding this comment

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

I would go with true by default for dynflow_console_authorize_with_ssl_client

Copy link
Member

Choose a reason for hiding this comment

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

Also, since it's a dynflow plugin, we can assume, that the console is dynflow as well, so we can shorten the option to console_authorize_with_ssl_client

@stbenjam
Copy link
Member

Great, thanks! ACK

@iNecas
Copy link
Member

iNecas commented Feb 16, 2016

Thanks @adamruzicka and @stbenjam

iNecas added a commit that referenced this pull request Feb 16, 2016
Fixes #11363 - Smart proxy dynflow console auth
@iNecas iNecas merged commit 0c7ab95 into theforeman:master Feb 16, 2016
@adamruzicka adamruzicka deleted the fix/11363-auth branch February 16, 2016 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants