You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our Prometheus and Jolokia examples are both exposing unsecured (http) endpoints. We should have them be secured (https) since that is how people will normally want to run their metric endpoints.
The text was updated successfully, but these errors were encountered:
I am looking into getting the Agent to use a system generated certificate. This will allow the agent's certificate to be signed by a known CA (the OpenShift CA), which means things like client based authentication may work with Jolokia (may work, as I am still having problems even with the extraClientChecks set to false). if we can get this to work, then a default configuration for Jolokia client based authentication will function properly.
Beyond this, we would also need to make sure that we modify the connection to endpoints so that we don't automatically trust all SSL connections. If we are going to pass username/passwords we need to make sure the endpoint we are talking to has been properly configured for that endpoint.
Our Prometheus and Jolokia examples are both exposing unsecured (http) endpoints. We should have them be secured (https) since that is how people will normally want to run their metric endpoints.
The text was updated successfully, but these errors were encountered: