so the server is doing a forward instead of a redirect so chrome client
*should* be safe
would a self-signed cert be flagged as "non-secure connection" in Chrome
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/2LXKVWYkOus%5B1-25%5D
The MSFT Certificate Server does not have a product name per se. We have an
internal Certificate Server in our AD infrastructure. In this use case I just
generate a key pair on the UNIX side in a JKS. Then create a Certificate
Signing Request (CSR) from that key. Then I sign it with our
Unfortunately im more of a nix guy
I take it windows has a CA server which will parse cert and lookup attrs (CN?)
to name-server?
what is the Microsoft CA server called?
if cert is parsed and keys match which name-server do you use to lookup attrs
(CN?) in that scenario?
Merci Eugene
Not really.
I have managed to generate a cert with a single common CN, sign that with my
internal CA and import that to the keystore that is referenced by the
Kafka-Rest Proxy. I then distribute that Java Keystore (JKS) to all of the
servers running the Rest API. The last part is to export
probably fighting an uphill battle sending cleartext POSTS and GETS with REST
calls
most apache server folk who secure HTTP 1.1 server will front end with CA
(provided by thawte,verisign,GeoTrust)
https://www.geotrust.com
We are looking at the Rest Proxy for our environment but we want to secure
connections to the Rest proxy via SSL AND Client Certificate authentication.
The SSL part is no big deal but I am struggling mightly with the client
authentication portion.
Does someone have some details on how to
