On Wed, Apr 05, 2017 at 10:38:48PM -0700, Wim Lewis wrote:
> With a bit of tweaking, I was able to generate a usable
> certificate by creating a second host entry,
> 'wildcard.blah.example.com', managed by blah.example.com, and then
> editing the leftmost label from 'wildcard' to '*' in all of the
With a bit of tweaking, I was able to generate a usable certificate by creating
a second host entry, 'wildcard.blah.example.com', managed by blah.example.com,
and then editing the leftmost label from 'wildcard' to '*' in all of the host's
LDAP entry's properties.
On Apr 3, 2017, at 6:41 PM,
On Mon, Apr 03, 2017 at 04:17:13PM -0700, Wim Lewis wrote:
> I'm trying to provision a client with a wildcard certificate[1]. I
> followed the procedure outlined in [2], but I'm not receiving the
> certificate I expect. The certificate's subject DN contains a
> wildcard string, but the SAN does
I'm trying to provision a client with a wildcard certificate[1]. I followed the
procedure outlined in [2], but I'm not receiving the certificate I expect. The
certificate's subject DN contains a wildcard string, but the SAN does not.
Since the SAN, not the subject name, is the relevant part of
