The only issue is there is no real good guide on how to do this. Is there
any more information that can be provided? What would really help is to see
the F5 VS, F5 SSL Profile, and how the ssl key was generated.
On Monday, July 9, 2012 8:05:22 AM UTC-4, olli...@googlemail.com wrote:
On
On Monday, 9 July 2012 06:44:16 UTC+1, Alan Evans wrote:
From what I can tell there is no need to use alternate names. You can
make the F5 appear to the clients to be the puppetmaster by leveraging
the F5 to do SSL offloading and part of the certificate verification
taking some load off
From what I can tell there is no need to use alternate names. You can
make the F5 appear to the clients to be the puppetmaster by leveraging
the F5 to do SSL offloading and part of the certificate verification
taking some load off your puppet masters. Even more though, since the
puppet
The best I was able to do is when you generate the certificate for the
puppet master you use dns alt names flag to specify the alternative
names for the puppet master. That is the only way I was able to make
it work in my environment with the F5.
On Sat, Jul 7, 2012 at 6:17 PM, Hai Tao
