Log in to ask questions, share your expertise, or stay connected to content. Don’t have a login? Join now.
No VIP
When I generate the CSR should it look like this :
CN:
cppm1.cppm.test.com
DNS:
cppm2.cppm.test.com,
IP:
10.2.100.101,
10.2.101.1102,
Check out the document here: http://support.arubanetworks.com/Documentation/tabid/77/DMXModule/512/Command/Core_Download/Default.aspx?EntryId=13734
I think you are looking for a clustered deployment.
Thanks Colin, so I guest it shouldn't matter if the SAN is FDQN is attached to a different IP address ?
CN:CPPM1.testing.com
SAN:
DNS:CPPM2.testing.com
IP:10.2.100.200
If you are using the same certificate for two different boxes, all their ip addresses and DNS names need to be in there.
"SAN – Subject Alternate Name
The subject alternative names (SubjectAltName) extension allows one SSL certificate to be used to secure one Web server with multiple names (such as a different DNS name, IP address or URI). Alternatively, the SubjectAltName extension can be used to secure up to two virtual Web servers using the same SSL certificate. "
"It is imperative that we configure the system with a Fully-Qualified-Domain-Name (FQDN). I’ve intentionally made an error to highlight that if you want to use a Subject Alternate Name (SAN) attribute in the certificate creation it must begin with uppercase DNS, IP or URI not lowercase letters. Multiple SAN’s entries can be entered comma delimited and there can be a mix of DNS and IP values."
Thanks for the confirmation
Victor,
Did we not cover this in email yesterday, or is this a different opportunity? ..... as Colin points out take a look at my CPPM PKI 101 Guide.
© Copyright 2024 Hewlett Packard Enterprise Development LPAll Rights Reserved.