> On 2 Dec 2020, at 19:04, Angel Bosch Mora wrote:
>
>> depending on your version of 389, look at "dsctl tls
>> import-ca"
>>
>> {william@ldapkdc 9:12} ~/development $ dsctl localhost tls import-ca
>> --help
>> usage: dsctl [instance] tls import-ca [-h] cert_path nickname
>>
>> positional
Hi abosch,
Have you looked at preconfiguring the cert db's with a wildcard cert from a CA
to avoid the request/sign dance?
Trev
On 2020-12-02, 1:04 AM, "Angel Bosch Mora" wrote:
[CAUTION: Non-UBC Email]
> depending on your version of 389, look at "dsctl tls
> import-ca"
> depending on your version of 389, look at "dsctl tls
> import-ca"
>
> {william@ldapkdc 9:12} ~/development $ dsctl localhost tls import-ca
> --help
> usage: dsctl [instance] tls import-ca [-h] cert_path nickname
>
> positional arguments:
> cert_path The path to the x509 cert to import as
depending on your version of 389, look at "dsctl tls import-ca"
{william@ldapkdc 9:12} ~/development $ dsctl localhost tls import-ca --help
usage: dsctl [instance] tls import-ca [-h] cert_path nickname
positional arguments:
cert_path The path to the x509 cert to import as a server CA
